Heroku vs self-hosted PaaS

1

Heroku

Heroku uses a concept they call dynos. A dyno is by default a container with 512MB of RAM that runs a part of a single application. To scale your app you simply add more dynos and Heroku will automatically load balance it for you. You can also have dynos running background jobs and such as well as schedulers to do cron-like things. If your app gets a lot of traffic then you can simply add more dynos to increase performance and Heroku will load balance between them automatically. Heroku offers four main kinds of dynos: Free, Hobby, Standard and Performance.

#Cloud Computing #Cloud Hosting #VPS 71 social mentions

2

Dokku

CapRover is in many ways similar to Dokku. It uses Docker for deployment just like Dokku but CapRover does not support buildpack deployments as it uses Dockerfiles only. This is not necessarily a bad thing since Dockerfile deployments are great in Dokku as well. You don’t have to write your own dockerfiles however for simple deployments as there are multiple defaults for popular stacks such as Node.js, PHP and Ruby. While Dokku uses its concept of plugins for databases and such, CapRover has what is called a “one click app”. Essentially these are applications and services that can be deployed through CapRovers GUI. Yeah that’s right, there is a GUI here as well. Simply pick the database or other service that you want and deploy it. You can then connect to it by using it’s name as there is an internal Docker network between all the containers running in CapRover.

#IT Automation #Backend As A Service #PaaS 12 social mentions

3

Flynn

Flynn was very promising when it was announced but it seems like the project is not getting anywhere. The company blog has not been updated in two years and there are multiple issues on the Github page asking if the project is abandoned. People have also reported that the project is buggy and does not work as well as it was intended. Flynn was announced before the rise of Kubernetes for example and that might explain why the project has slowed down. I would not use Flynn in production today for these reasons.

#Developer Tools #DevOps Tools #Cloud Computing 2 social mentions

4

Rancher

All in all I’m intrigued by Rancher but since I am looking for something simple then it is too advanced and resource intensive for my small side projects. I will however look into Rancher a bit more later and try to deploy one of my projects to it. That will probably be a blog post in it’s own!

#DevOps Tools #Developer Tools #Continuous Integration And Delivery 24 social mentions

5

CapRover

CapRover is in many ways similar to Dokku. It uses Docker for deployment just like Dokku but CapRover does not support buildpack deployments as it uses Dockerfiles only. This is not necessarily a bad thing since Dockerfile deployments are great in Dokku as well. You don’t have to write your own dockerfiles however for simple deployments as there are multiple defaults for popular stacks such as Node.js, PHP and Ruby. While Dokku uses its concept of plugins for databases and such, CapRover has what is called a “one click app”. Essentially these are applications and services that can be deployed through CapRovers GUI. Yeah that’s right, there is a GUI here as well. Simply pick the database or other service that you want and deploy it. You can then connect to it by using it’s name as there is an internal Docker network between all the containers running in CapRover.

#PaaS #Cloud Computing #Container Tools 105 social mentions