Google App Engine vs Heroku vs OpenShift

Google App Engine
Google App Engine

2.4K
155
606
Heroku
Heroku

7.1K
887
3.1K
OpenShift
OpenShift

428
169
466
- No public GitHub repository available -
- No public GitHub repository available -

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.

What is OpenShift?

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose Google App Engine?
Why do developers choose Heroku?
Why do developers choose OpenShift?
What are the cons of using Google App Engine?
What are the cons of using Heroku?
What are the cons of using OpenShift?
    Be the first to leave a con
    What companies use Google App Engine?
    What companies use Heroku?
    What companies use OpenShift?
    What are some alternatives to Google App Engine, Heroku, and OpenShift?
    windows azure
    Microsoft Corporation is an American multinational technology company with headquarters in Redmond, Washington.
    Amazon Web Services
    It provides on-demand cloud computing platforms to individuals, companies and governments. It offers reliable, scalable, and inexpensive cloud computing services.
    DigitalOcean
    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel.
    AWS Lambda
    AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
    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
    What tools integrate with Google App Engine?
    What tools integrate with Heroku?
    What tools integrate with OpenShift?
    Decisions about Google App Engine, Heroku, and OpenShift
    Jerome Dalbert
    Jerome Dalbert
    Senior Backend Engineer at StackShare · | 7 upvotes · 14.8K views
    atGratify CommerceGratify Commerce
    AWS Elastic Beanstalk
    Heroku
    Rails
    #PaaS

    When creating the web infrastructure for our start-up, I wanted to host our app on a PaaS to get started quickly.

    A very popular one for Rails is Heroku, which I love for free hobby side projects, but never used professionally. On the other hand, I was very familiar with the AWS ecosystem, and since I was going to use some of its services anyways, I thought: why not go all in on it?

    It turns out that Amazon offers a PaaS called AWS Elastic Beanstalk, which is basically like an “AWS Heroku”. It even comes with a similar command-line utility, called "eb”. While edge-case Rails problems are not as well documented as with Heroku, it was very satisfying to manage all our cloud services under the same AWS account. There are auto-scaling options for web and worker instances, which is a nice touch. Overall, it was reliable, and I would recommend it to anyone planning on heavily using AWS.

    See more
    Interest over time
    Reviews of Google App Engine, Heroku, and OpenShift
    Review ofHerokuHeroku

    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 ofHerokuHeroku

    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 ofGoogle App EngineGoogle 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 ofOpenShiftOpenShift

    I needed a PaaS provider that didn't drop all the time and it's hard to find a good option for PHP applications. Openshift takes care of it. They are a little behind on PHP versions, but that can be solved with a custom cartridge. It requires a little more elbow grease to get rolling when you want to implement something they don't already have, but their quickstarts are great to get rolling with the basics quickly.

    Review ofHerokuHeroku

    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 ofHerokuHeroku

    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 ofHerokuHeroku

    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 ofGoogle App EngineGoogle App Engine

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

    How developers use Google App Engine, Heroku, and OpenShift
    Avatar of StackShare
    StackShare uses HerokuHeroku

    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.

    Avatar of Casey Smith
    Casey Smith uses Google App EngineGoogle 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.

    Avatar of StackShare
    StackShare uses HerokuHeroku

    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.

    Avatar of Lawrence Cheuk
    Lawrence Cheuk uses Google App EngineGoogle 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.

    Avatar of Tim Lucas
    Tim Lucas uses HerokuHeroku

    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.

    Avatar of Jeff Flynn
    Jeff Flynn uses HerokuHeroku

    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.

    Avatar of Matt Welke
    Matt Welke uses HerokuHeroku

    Used for proofs of concept and personal projects where I want to remain in a free tier (as opposed to a service like DigitalOcean), and application state must outlive an HTTP request/response cycle.

    Heroku Postgres sometimes used as a free tier PostgreSQL managed database linked to non-Heroku apps, for example AWS Lambda.

    Avatar of kelumkps
    kelumkps uses OpenShiftOpenShift

    SG-TravelBuddy server application is hosted on Red Hat OpenShift Online (v3). SG-TravelBuddy mobile (Android) app is connecting to this server for data operations.

    Avatar of CommentBox.io
    CommentBox.io uses Google App EngineGoogle App Engine

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

    Avatar of Abhijeet Gokar
    Abhijeet Gokar uses Google App EngineGoogle App Engine

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

    Avatar of Vamsi Krishna
    Vamsi Krishna uses Google App EngineGoogle App Engine

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

    Avatar of InApplet
    InApplet uses OpenShiftOpenShift

    Servidor das aplicações de Back-end

    Avatar of azawisza
    azawisza uses OpenShiftOpenShift

    Main cloud infrastructure provider

    Avatar of Miyuru Sankalpa
    Miyuru Sankalpa uses OpenShiftOpenShift

    To host the blog powered by ghost

    Avatar of AyeDeals
    AyeDeals uses OpenShiftOpenShift

    OpenShift is our PaaS.

    How much does Google App Engine cost?
    How much does Heroku cost?
    How much does OpenShift cost?