Apache Mesos vs. IBM Cloud Private

Mesos is really great when you have a big datacenter with many different applications and use cases. It will help you to optimize the resource usage, being a centralized API for your infrastructure. It will not suit well for small companies that just need to deploy a web app. In this case, I would recommend something smaller.

Incentivized

IBM Cloud Private is well suited for SaaS models.

Incentivized

• Mesos may have many frameworks. If you have Mesos installed on your servers, you may use it for many kinds of tasks. Today we're running only web applications but the idea is to install a different framework for big data soon.
• There is a good community growing around it.

Incentivized

• There is a large variety of services available on IBM Cloud.
• This is my first experience with a PaaS and I haven’t had any major problems navigating around it.
• It is easy to deploy applications and services on IBM Cloud.

Incentivized

• Unreliable deployments that would fail for no good reason. Sometimes our Docker container would be "restarting" forever because Mesos thought it didn't have enough resources to start the container.
• Impossibly slow UI. Built in React under the hood with a lot of bloatware backed in, so loading the Mesos UI on a slow internet connection was painful.
• No real logging solution - it would stream "console.log()" output to the UI, but searching for logs wasn't really possible without downloading a huge file.
• No built-in support for redeploying containers from a CI. We had to create a service whose whole job was to expose an HTTP endpoint that restarted a container, and then made Circle CI ping the endpoint whenever we wanted to redeploy.

Incentivized

• More hands on training outside of virtual classes would be helpful.

Incentivized

No real support channel, the Mesos GitHub issues list was the only one we found and it wasn't particularly helpful.

Incentivized

Kubernetes is by far the best choice. More reliable and better developer experience. Mesos is prone to sporadic failures and not really designed to handle CI/CD-based deployments. Docker Cloud once shut down our entire cluster for "upgrades" without giving us any warning.

Incentivized

With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.

Incentivized

• Developers needed to spend hours waiting to verify that their supposedly automated CD deploys actually went through.
• Lots of late night and early morning calls that Mesos deploys are hanging again.
• 10-20 hours spent building a custom service just to integrate Mesos with a CD provider.

Incentivized

• N/A
• N/A
• N/A

Incentivized