AWS Elastic Beanstalk vs Google App Engine vs Heroku

Need advice about which tool to choose?Ask the StackShare community!

AWS Elastic Beanstalk

1.9K
1.6K
+ 1
240
Google App Engine

7K
5.3K
+ 1
614
Heroku

18K
13.7K
+ 1
3.2K
Decisions about AWS Elastic Beanstalk, Google App Engine, and Heroku

I'm transitioning to Render from heroku. The pricing scale matches my usage scale, yet it's just as easy to deploy. It's removed a lot of the devops that I don't like to deal with on setting up my own raw *nix box and makes deployment simple and easy!

Clustering I don't use clustering features at the moment but when i need to set up clustering of nodes and discoverability, render will enable that where Heroku would require that I use an external service like redis.

Restarts The restarts are annoying. I understand the reasoning, but I'd rather watch my service if its got a memory leak and work to fix it than to just assume that it has memory leaks and needs to restart.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS Elastic Beanstalk
Pros of Google App Engine
Pros of Heroku
  • 77
    Integrates with other aws services
  • 65
    Simple deployment
  • 44
    Fast
  • 28
    Painless
  • 16
    Free
  • 3
    Independend app container
  • 3
    Well-documented
  • 2
    Postgres hosting
  • 2
    Ability to be customized
  • 144
    Easy to deploy
  • 108
    Auto scaling
  • 81
    Good free plan
  • 64
    Easy management
  • 58
    Scalability
  • 36
    Low cost
  • 33
    Comprehensive set of features
  • 29
    All services in one place
  • 23
    Simple scaling
  • 20
    Quick and reliable cloud servers
  • 5
    Granular Billing
  • 4
    Easy to develop and unit test
  • 3
    Monitoring gives comprehensive set of key indicators
  • 2
    Create APIs quickly with cloud endpoints
  • 2
    Really easy to quickly bring up a full stack
  • 1
    Mostly up
  • 1
    No Ops
  • 702
    Easy deployment
  • 460
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 154
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 47
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 11
    Great customer support
  • 8
    GitHub integration
  • 6
    No-ops
  • 5
    Painless & well documented
  • 3
    Just works
  • 3
    Free
  • 2
    MySQL extension
  • 2
    Great UI
  • 2
    PostgreSQL forking and following
  • 2
    I love that they make it free to launch a side project

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Elastic Beanstalk
Cons of Google App Engine
Cons of Heroku
  • 2
    Charges appear automatically after exceeding free quota
  • 0
    Slow deployments
    Be the first to leave a con
    • 22
      Super expensive
    • 6
      No usable MySQL option
    • 6
      Not a whole lot of flexibility
    • 5
      Storage
    • 4
      Low performance on free tier

    Sign up to add or upvote consMake informed product decisions

    What is AWS Elastic Beanstalk?

    Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

    What is Google App Engine?

    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.

    What is Heroku?

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use AWS Elastic Beanstalk?
    What companies use Google App Engine?
    What companies use Heroku?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with AWS Elastic Beanstalk?
    What tools integrate with Google App Engine?
    What tools integrate with Heroku?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Sep 29 2020 at 7:36PM

    WorkOS

    +17
    6
    2299
    +8
    6
    2172
    +47
    46
    68298
    +23
    12
    6316
    +25
    7
    2794
    Jun 19 2015 at 6:37AM

    ReadMe.io

    +25
    11
    1486
    +24
    13
    16650
    What are some alternatives to AWS Elastic Beanstalk, Google App Engine, and Heroku?
    AWS CodeDeploy
    AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.
    Docker
    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
    AWS CloudFormation
    You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
    Azure App Service
    Quickly build, deploy, and scale web apps created with popular frameworks .NET, .NET Core, Node.js, Java, PHP, Ruby, or Python, in containers or running on any operating system. Meet rigorous, enterprise-grade performance, security, and compliance requirements by using the fully managed platform for your operational and monitoring tasks.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    See all alternatives
    Reviews of AWS Elastic Beanstalk, Google App Engine, and Heroku
    Review of
    Heroku

    I use Heroku, for almost any project of mine. Their free plan is awesome for testing, solo developers or your startup and its almost impossible to not cover you somehow. Adding an add on is a simple command away and I find it easy to use it both on my Windows PC or my Linux laptop. Their documentation, covers almost everything. In particular I have used Heroku for Spring, Django and AngularJS. I even find it easier to run my project on my local dev with foreman start, than ./manage.py runserver (for my django projects). There is no place like Heroku for the developer!

    Review of
    Heroku

    Can't beat the simplicity of deploying and managing apps, the pricing is a bit high, but you are paying for those streamlined tools. However, after several experiences of tracing issues back to Heroku's stack, not having visibility into what they are doing has prompted moving two applications off of it and on to other more transparent cloud solutions. Heroku is amazing for what it is, hosting for early stage products.

    Review of
    Google App Engine

    With Cloud Endpoints you can create and deploy mobile backend in one hour or less. And it is free (until you need extra scale). I would not recommend to use Java - python is faster and has all new appengine features.

    Pros: everything is in one place: task queue, cron, backend instances for data processing, datastore, mapreduce. Cons: you cannot easily move your code from GAE. Even with special 3rd party services.

    Review of
    Heroku

    I've been using Heroku for 3 years now, they have grown super fast and each time they're improving their services. What I really like the most is how easily you can show to your client the advances on you project, it would take you maximum 15 minutes to configure two environments (Staging/Production). It is simply essential and fantastic!

    Review of
    Heroku

    I liked how easy this was to use and that I could create some proof of concepts without have to pay. The downside for NodeJS is remote debugging. Pretty much have to depend on logging where Azure allows remote debugging with Node Inspector.

    Review of
    Heroku

    Using Heroku takes away all the pains associated with managing compute and backing services. It may require a little extra optimisation and tweaks, but these constraints often make your app better anyway.

    Review of
    Google App Engine

    With Cloud Endpoints you can create and deploy mobile backend in one hour or less.

    How developers use AWS Elastic Beanstalk, Google App Engine, and Heroku
    StackShare uses
    Heroku

    Not having to deal with servers is a huge win for us. There are certainly trade-offs (having to wait if the platform is down as opposed to being able to fix the issue), but we’re happy being on Heroku right now. Being able to focus 100% of our technical efforts on application code is immensely helpful.

    Two dynos seems to be the sweet spot for our application. We can handle traffic spikes and get pretty consistent performance otherwise.

    We have a total of four apps on Heroku: Legacy Leanstack, StackShare Prod, StackShare Staging, StackShare Dev. Protip: if you’re setting up multiple environments based on your prod environment, just run heroku fork app name. Super useful, it copies over your db, add-ons, and settings.

    We have a develop branch on GitHub that we push to dev to test out, then if everything is cool we push it to staging and eventually prod. Hotfixes of course go straight to staging and then prod usually.

    Casey Smith uses
    Google App Engine

    PaaS for back-end components, including external data ingestion APIs, front-end web service APIs, hosting of static front-end application assets, back-end data processing pipeline microservices, APIs to storage infrastructure (Cloud SQL and Memcached), and data processing pipeline task queues and cron jobs. Task queue fan-out and auto-scaling of back-end microservice instances provide parallelism for high velocity data processing.

    StackShare uses
    Heroku

    We keep the Metrics tab open while we load test, and hit refresh to see what’s going on: heroku metric

    I would expect the graphs to expand with some sort of detail, but that’s not the case. So these metrics aren’t very useful. The logs are far more useful, so we just keep the tail open while we test.

    Lawrence Cheuk uses
    Google App Engine

    checking a swap require a lot of cpu resource, roster normally come out same day of month, every month, at a particular time. Which make very high spike, our flag ship product, iSwap, with the capability looking swap possibility with 10000 other rosters base on user critieria, you need a cloud computing give you this magnitude of computing power. gae did it nicely, user friendly, easy to you, low cost.

    Tim Lucas uses
    Heroku

    Heroku runs the web and background worker processes. Auto-deployments are triggered via GitHub commits and wait for the Buildkite test build to pass. Heroku pipelines with beta release phase execution (for automatically running database migrations) allowed for easy manual testing of big new releases. Web and worker logs are sent to Papertrail.

    Jeff Flynn uses
    Heroku

    As much as I love AWS EC, I prefer Heroku for apps like this. Heroku has grown up around Rails and Ruby, massive set of add-ons that are usually one-click setup, and I once had to perform an emergency app scale-up a that I completed in seconds from my mobile phone whilst riding the Bangkok subway. Doesn't get much easier than that.

    danlangford uses
    Heroku

    With its complimentary SSL (on *.herokuapp.com) we can test everything. Our dev branch is built and deployed out to Heroku. Testing happens out here. not production cause $20/mo is TOO much to pay for the ability to use my own SSL purchased elsewhere.

    ONLICAR uses
    AWS Elastic Beanstalk

    Elastic Beanstalk gives us a managed platform for our front end servers to make sure that traffic is never overloading our servers and that deployments are always successful.

    CommentBox.io uses
    Google App Engine

    App engine fills in the gaps in the increasingly smaller case where it's necessary for us to run our own APIs.

    Lumanu uses
    AWS Elastic Beanstalk

    Elastic Beanstalk manages our environments. We rely on it to manage rolling out new versions of services.

    Flux Work uses
    AWS Elastic Beanstalk

    Easy to get started. Essentially a package of several AWS products integrated for you.

    Abhijeet Gokar uses
    Google App Engine

    Very easy to make cloud computing of ML models , and use containers like Kubernetes.

    Vamsi Krishna uses
    Google App Engine

    Cloud instances to run our app, Cloud MySQL , Network Load Balancer

    Daniel Pupius uses
    AWS Elastic Beanstalk

    For convenience I use Elastic Beanstalk to host all my sites.

    Undisclosed, Do Not Contact or Spam Please uses
    AWS Elastic Beanstalk

    All server-side deployments go to one of 5 EB environments.