Clever Cloud vs Flynn vs Heroku

Get Advice Icon

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

Clever Cloud
Clever Cloud

187
196
+ 1
969
Flynn
Flynn

12
23
+ 1
10
Heroku
Heroku

8.8K
6.4K
+ 1
3.1K
- No public GitHub repository available -
- No public GitHub repository available -

What is Clever Cloud?

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

What is Flynn?

Flynn lets you deploy apps with git push and containers. Developers can deploy any app to any cluster in seconds.

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 Clever Cloud?
Why do developers choose Flynn?
Why do developers choose Heroku?

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

    Be the first to leave a con
    What companies use Clever Cloud?
    What companies use Flynn?
    What companies use Heroku?

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

    What tools integrate with Clever Cloud?
    What tools integrate with Flynn?
    What tools integrate with Heroku?

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

    What are some alternatives to Clever Cloud, Flynn, and Heroku?
    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.
    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.
    Apollo
    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.
    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.
    Azure Websites
    Azure Websites is a fully managed Platform-as-a-Service (PaaS) that enables you to build, deploy and scale enterprise-grade web Apps in seconds. Focus on your application code, and let Azure take care of the infrastructure to scale and securely run it for you.
    See all alternatives
    Decisions about Clever Cloud, Flynn, and Heroku
    Jerome Dalbert
    Jerome Dalbert
    Senior Backend Engineer at StackShare · | 7 upvotes · 20.6K 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 · | 21 upvotes · 441K 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