Dokku vs. IBM Cloud Functions

If you have your own in-house servers or have a cloud server with the freedom to configure any PaaS that you want, then Dokku is for you. So far, I have never run into a scenario where Dokku was not able to fit my needs, after deploying many different types of applications with varying frameworks, languages, and connected services. If you already have a PaaS available, however, Dokku may not be for you.

Incentivized

IBM Cloud Functions [is] not the worse product on the IBM cloud. I decided to write this review as I thought it would be balanced. I would still use functions to set up a serverless architecture where execution time is pretty quick and the code is relatively simple. I wouldn't use IBM Cloud Functions for async calls obviously, as costs could be higher. The functions documentation is lacking in terms of CI/CD, and there are unexplainable errors occurring - like the network connection that I mentioned. So I wouldn't just rely on IBM Cloud Functions too much for the entire system, but make sure it's diversified.

• Dockerfile deployments are an incredibly simple and straightforward way to spin up applications.
• The docker-options plugin allows endless direct configuration of options passed to different docker lifecycle stages.

Incentivized

• Great substitute for a simple API calls to run non-complicated code.
• Easy way to run Python/Java/Javascript to get something done.
• File validation.

Incentivized

• Dokku might overreach on its assumptions about how you want to host your app, using its own VHOSTS plugin by default. This may be a pro or a con depending on what you want.
• Proxy port configuration can be somewhat difficult, with Dokku resetting any pre-deployment configuration to "smart" defaults on the first deployment.

Incentivized

• Billing can be a hassle, not the most responsive customer service/support team
• Handles & executes most functionalities, but other platforms offer more scalability if you're seeking consistent and stable growth

Incentivized

Dokku is incredibly well documented and also takes advantage of the documentation and community of Heroku, being essentially the same thing, but in the case that you encounter an actual bug or issue, it can take time for a fix to make it into a new version. Since you manage Dokku yourself, there is no support team to call for help.

Incentivized

Dokku is essentially the same thing as Heroku, except maintained by you on the platform of your choice. If you have any experience using Heroku, then you will feel right at home using Dokku. Dokku is an entirely free to use PaaS, requiring only that you have a platform to deploy it on, making it far more versatile than Heroku in my opinion.

Incentivized

• ICF is a lightweight service and does not require runtime configurations
• Scalable on demand and hence there is no need to pay for runtime costs

Incentivized

• Since there's no investment besides a little time to set up, the return has been overwhelmingly positive.
• Deploying a new app is incredibly quick and easy.

Incentivized

• It directly affected our expenses since we do not need to deploy and maintain a set of separate applications.
• It allowed us to pay for only the amount of time cloud functions run.
• It saved on maintenance and monitoring of the applications it replaced.

Incentivized