This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

Heroku or Amazon Web Services – Which is Best for Your Startup?

  • 182859 views
  • 7 min
  • Jan 06, 2020
Sviatoslav A.

Sviatoslav A.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Share

Amazon Web Services (AWS) and Heroku are two commonly used cloud services that let us deploy, monitor, and scale web and mobile apps.

Both services provide us with cloud computing resources and are great for hosting applications.

But if you’re building your first mobile or web application, how can you decide which of these options – AWS or Heroku – is best for your application?

Choosing a hosting service becomes even harder when we take a glance at the number of products Amazon Web Services offer. It’s easy to get lost.

Screenshot of all AWS products

AWS provides a wide variety of products, making it difficult to quickly choose the right solution for your needs. And we haven’t even started considering Heroku!

Let’s dive into the features of AWS and Heroku – and consider the key solutions they offer – to figure out your best option!

AWS vs Heroku for Startups

If we search for a comparison of Heroku and AWS, we’ll see a bunch of articles that juxtapose AWS Elastic Compute Cloud (EC2) with Heroku. But is the Heroku vs AWS Elastic Beanstalk comparison reasonable? Comparing these two products isn’t very logical for several reasons, as we’ll explain shortly. We'll also mention what are the advantages and disadvatanges of one hosting provider vs another.

What are Heroku and AWS?

AWS Elastic Compute Cloud

Elastic Compute Cloud (EC2) is an Infrastructure as a Service product, and is Amazon’s flagship offering. Before we’re able to deploy an application on Elastic Compute Cloud, we have to develop server infrastructure that will suit our application.

But what does that look like? Put simply, we’ll need to manually configure and maintain virtualized servers that run our application. We also add database instances; choose and set up an operating system; and set up a load balancer to spread the load across multiple application servers. On top of that, we must select a CPU and amounts of RAM and storage that satisfy our application’s need. We’ll also install backup servers and hook them up to the main servers.

Elastic Compute Cloud provides us only with the building blocks. Our task is to select the best blocks for our application and actively manage them, not only set them up. At many web development companies, a dedicated DevOps engineer is responsible for provisioning EC2 instances, controlling application deployment, and orchestrating EC2 infrastructure (deciding how these ‘building blocks’ interact with each other).

Heroku

Now let’s see what Heroku offers. Heroku is a Platform as a Service (PaaS) product based on AWS, and is vastly different from Elastic Compute Cloud. It’s very important to differentiate ‘Infrastructure as a Service’ and ‘Platform as a Service’ solutions as we consider deploying and supporting our application using these two solutions.

Heroku is way simpler to use than AWS Elastic Compute Cloud. Perhaps it’s even too simple. But there’s a good reason for this simplicity. This platform equips us with a ready runtime environment and application servers. Plus, we benefit from seamless integration with various development instruments, a pre-installed operating system, and redundant servers.

Therefore, we don’t need to think about infrastructure management, unlike with AWS EC2. We only need to choose a subscription plan and change our plan when necessary.

This is how a conversation with Heroku might go:

– Hey, we need to rapidly send a lot of cached data to our users!
– Here you go: Redis is ready!

– Hey, we need more dynos to handle HTTP traffic!
– Yeah, just run the following command in CLI and specify the number of instances, e.g. three web dynos: $ heroku ps:scale web=3

– And what about a PostgreSQL instance?
– You need one – you get one! Run this command in CLI: $ heroku addons:create heroku-postgresql:hobby-dev
– Thanks!

– We need to restart our dynos! A new app version is coming!
– Just deploy your updated app, I’ll handle this.

As we can see, Heroku conveniently takes care of the details. Thus, we can throw all our efforts into application development. You only need a web developer – or multiple developers – to create an application and push it to Heroku using Git. All management is done via the Command Line Interface or in the Dashboard.

Сomparing AWS Elastic Compute Cloud to Heroku is like comparing a microwave to a toaster. Both devices are used for heating food, but they work differently. Maybe this metaphor isn’t the most apt, but it gets across the general point: We use AWS EC2 and Heroku to reach different goals.

So, to be reasonable, we must mention another AWS product that is a direct competitor to Heroku. This product is called Elastic Beanstalk, and it’s also a Platform as a Service product.

AWS Elastic Beanstalk

In short, Heroku vs AWS means Heroku vs Elastic Beanstalk. AWS offers Elastic Beanstalk to simplify application deployment.

We deploy applications on AWS Elastic Beanstalk by running commands in a Command Line Interface (provided by AWS) or by using the Management Console. After deployment, Elastic Beanstalk manages infrastructure without our control.

We generally don’t need to set up capacity provisioning, load balancing, or scaling, although we’re still able to get access to the infrastructure, if necessary, and save multiple configuration options for our application. Elastic Beanstalk uses EC2 instances to host your application, so migrating from AWS Beanstalk to EC2 is easy. And that’s great.

AWS vs Heroku Features

For a quick comparison of the two services, check out the table below:

Service AMAZON WEB SERVICES HEROKU

Offered by

Amazon
hosted on proprietary servers

Salesforce
hosted on Amazon Web Services

Pricing

Pay-as-you-go

Pay-as-you-go

Main Offerings

Platform as a Service
(Elastic Beanstalk)

Infrastructure as a Service
(Elastic Compute Cloud)

Platform as a Service

Concept

Ready platform for rapid app deployment
(Elastic Beanstalk)

Infrastructure, which must be set up before deployment and managed afterwards
(Elastic Compute Cloud)

Ready platform for rapid app deployment

Supported platforms

Runs environments for Ruby, NodeJS, Python, Go, Docker, PHP, and .NET apps

Runs environments for Ruby, Python, PHP, Clojure, Go, Java, Scala, and Node.js apps

Scaling

Supports automatic scaling for EC2 and Beanstalk based on time and metrics

Can set up the AutoScale feature before deploying your application

Supports manual scaling with the Scaling slider in Dashboard or via a Command Line Interface

Geographic
availability

Throughout the world

US and Europe

Main Features

Elastic Beanstalk
Capacity Provisioning
Load Balancing
Auto-Scaling
App Health Monitoring

Elastic Compute Cloud
Ready templates for deployment
Multiple configurations (CPU, RAM, etc.)

Capacity Provisioning
Database Rollback
Application Rollback
Manual Vertical and Horizontal Scaling
App Health Monitoring
Full GitHub Integration

Architecture

Web server/load balancer
Platform
Operating System
Application tier
Database tier

Web server/load balancer
Platform
Operating System
Application tier
Database tier

Built-in Tools for Management and Monitoring

AWS Management Console
AWS Command Line Interface (AWS CLI)
AWS CloudWatch

Heroku Command Line
Heroku Application Metrics
Heroku Connect
Heroku Status

Service Level
Agreements

Available for Elastic Compute Cloud

Available for Enterprise projects

Conclusion

When choosing between AWS and Heroku, you primarily need to consider the costs. Will it cost less for you to manage infrastructure yourself, or is it cost-effective for you to reply on a ready (but somewhat costly) platform that manages your infrastructure for you?

In summary, you should use AWS Elastic Compute Cloud when:

  • You need infrastructure flexibility from the first deployment of your application.
  • You can afford a DevOps engineer or several DevOps engineers to manage the infrastructure.
  • You’re ready to spend more time deploying new versions of your app.
  • Your project demands great computational resources.

And you should use PaaS solutions when:

  • You need to deploy and test a Minimum Viable Product.
  • You need to improve your application quickly after getting feedback from users.
  • You can’t afford a DevOps engineer (or engineers).
  • Your project doesn’t demand that many computational resources.

If you do choose Amazon Web Services, it’s important to make sure that the company you’re working with has experience managing AWS infrastructure. And if rapid application development is your highest priority, consider Heroku or Beanstalk. Keep in mind that you can always switch between the PaaS and IaaS solutions should hosting plans change or your application demands a custom infrastructure. Still, it’s best to start with the right service right away.

CONTENTS

Authors:

Sviatoslav A.

Sviatoslav A.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Rate this article!

Nay
So-so
Not bad
Good
Wow
66 rating, average 4.52 out of 5

Share article with

Comments (3)
Anudeep Bichal
Anudeep Bichal over 6 years ago
Nice guidelines for the people interested in startups, clarity in your post is good, and I could assume you are an expert on this subject.
Reply
Sviatoslav A.
Sviatoslav A. over 6 years ago
Thank you for your comment! We appreciate your feedback and we'll keep on delighting you with useful posts!
Reply
IICT Chrompet
IICT Chrompet over 4 years ago
Thank you
Reply

Subscribe via email and know it all first!