Get Advice Icon

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

Dokku
Dokku

101
91
+ 1
58
Google App Engine
Google App Engine

2.9K
1.9K
+ 1
606
Heroku
Heroku

8.1K
5.8K
+ 1
3.1K
- No public GitHub repository available -
- No public GitHub repository available -

What is Dokku?

Docker powered mini-Heroku. The smallest PaaS implementation you've ever seen.

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.
Get Advice Icon

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

Why do developers choose Dokku?
Why do developers choose Google App Engine?
Why do developers choose Heroku?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      Jobs that mention Dokku, Google App Engine, and Heroku as a desired skillset
      What companies use Dokku?
      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 Dokku?
      What tools integrate with Google App Engine?
      What tools integrate with Heroku?
        No integrations found

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

        What are some alternatives to Dokku, Google App Engine, and Heroku?
        Flynn
        Flynn lets you deploy apps with git push and containers. Developers can deploy any app to any cluster in seconds.
        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
        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.
        Rancher
        Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
        Docker Compose
        With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
        See all alternatives
        Decisions about Dokku, Google App Engine, and Heroku
        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 7 upvotes · 18.9K views
        atGratify CommerceGratify Commerce
        Rails
        Rails
        Heroku
        Heroku
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        #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
        Russel Werner
        Russel Werner
        Lead Engineer at StackShare · | 19 upvotes · 247.7K views
        atStackShareStackShare
        React
        React
        Glamorous
        Glamorous
        Apollo
        Apollo
        Node.js
        Node.js
        Rails
        Rails
        Heroku
        Heroku
        GitHub
        GitHub
        Amazon S3
        Amazon S3
        Amazon CloudFront
        Amazon CloudFront
        Webpack
        Webpack
        CircleCI
        CircleCI
        Redis
        Redis
        #StackDecisionsLaunch
        #SSR
        #Microservices
        #FrontEndRepoSplit

        StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

        Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

        #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

        See more
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Heroku
        Heroku
        Ruby
        Ruby
        Rails
        Rails
        Amazon RDS for PostgreSQL
        Amazon RDS for PostgreSQL
        MariaDB
        MariaDB
        Microsoft SQL Server
        Microsoft SQL Server
        Amazon RDS
        Amazon RDS
        AWS Lambda
        AWS Lambda
        Python
        Python
        Redis
        Redis
        Memcached
        Memcached
        AWS Elastic Load Balancing (ELB)
        AWS Elastic Load Balancing (ELB)
        Amazon Elasticsearch Service
        Amazon Elasticsearch Service
        Amazon ElastiCache
        Amazon ElastiCache

        We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.

        We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.

        In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.

        Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache

        See more
        Heroku
        Heroku
        OpenShift
        OpenShift
        Docker
        Docker

        Heroku vs OpenShift. I've never decided which one is better. Heroku is easier to configure. Openshift provide a better machine for free. Heroku has many addons for free. I've chosen Heroku because of easy initial set-up. I had deployment based on git push. I also tried direct deployment of jar file. Currently Heroku runs my Docker image. Heroku has very good documentation like for beginners. So if you want to start with something, let's follow Heroku. On the other hand OpenShift seems like a PRO tool supported by @RedHat.

        See more
        Gunicorn
        Gunicorn
        uWSGI
        uWSGI
        Heroku
        Heroku
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk

        I use Gunicorn because does one thing - it’s a WSGI HTTP server - and it does it well. Deploy it quickly and easily, and let the rest of your stack do what the rest of your stack does well, wherever that may be.

        uWSGI “aims at developing a full stack for building hosting services” - if that’s a thing you need then ok, but I like the principle of doing one thing well, and I deploy to platforms like Heroku and AWS Elastic Beanstalk where the rest of the “hosting service” is provided and managed for me.

        See more
        Munkhtegsh Munkhbat
        Munkhtegsh Munkhbat
        Software Engineer Consultant at LoanSnap · | 9 upvotes · 25.6K views
        graphql-yoga
        graphql-yoga
        Prisma
        Prisma
        PostgreSQL
        PostgreSQL
        styled-components
        styled-components
        Heroku
        Heroku
        React
        React
        Apollo
        Apollo
        GraphQL
        GraphQL
        #Backend
        #Frontend

        In my last side project, I built a web posting application that has similar features as Facebook and hosted on Heroku. The user can register an account, create posts, upload images and share with others. I took an advantage of graphql-subscriptions to handle realtime notifications in the comments section. Currently, I'm at the last stage of styling and building layouts.

        For the #Backend I used graphql-yoga, Prisma, GraphQL with PostgreSQL database. For the #FrontEnd: React, styled-components with Apollo. The app is hosted on Heroku.

        See more
        Interest over time