Apache Mesos vs. Podman.io

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

While it always depends on your use case, I believe security concerns of need for root user is a concern, so it is worth considering daemonless container service over Docker, which works just as good and has support for docker compose. Another good reason is the licensing for enterprise usage, which podman has no restrictions for. It’s also a great choice for OpenShift integration, which is seamless and works well with Rancher as well.

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

• It’s daemonless, so somewhat more secure.
• It works exceptionally well and is compatible with Docker compose
• Podman Desktop actually makes individual usage also pretty easy.
• It can be used as Docker alternative with almost no additional steps

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

• Podman desktop is getting more stable with each version, but does need more UX friendliness as well.
• Official support for development tools and IDEs is missing for most tools
• It works well with Kubernetes, but I wouldn’t mind additional improvements

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

Podman is Daemonless, lightweight and doesn’t charge us for commercial usage, so it’s a relief for startups. Minikube and Rancher are a bit more complex for our use cases; so we keep things simple, fast and secure with Podman that can easily be managed with Podman Desktop and other works with our docker-compose based projects without issues.

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

• We definitely feel more secure.
• We do not suffer from memory or cpu overuses as it uses fedora coreOS which is lightweight
• We do not have to worry about license payments for our basic usages.
• It’s open source so quick fixes imminent with maximum transparency.

Incentivized