CloudFoundry vs. Dokku

It's well suited if:

• The organization has large number of applications that needs to be deployed frequently.
• The organization is tied to the DevOps mindset.
• The organization has programs in different languages.
• The applications does not need EJB's support that servers like web logic provide.

It's less suited if:

• The applications needs security configuration within the same CloudFoundry instance.
• The organization, for whatever reason does not want developers to manage the instances.

Incentivized

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

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Incentivized

• 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

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

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

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

While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.

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

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

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