TrustRadius Insights for Apache Mesos are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Easy Setup: Many users have found it incredibly easy to set up and get running in a cluster on standard hardware. They appreciate the straightforward software implementation of Mesos and its API-based nature, which contributes to its ease of use.
Stability: Users highly value the stability of Mesos, as they rarely encounter problems that are due to Mesos itself. This reliability allows them to confidently rely on Mesos for their distributed systems without worrying about frequent issues or disruptions.
Support for Docker Containers: Several reviewers emphasize the criticality of the support for running tasks within Docker containers. They find the Docker Containerizer important and appreciate the seamless integration with Mesos, enabling efficient task isolation and abstraction of physical resources from VMs or machines or applications.
We used Mesos to orchestrate and deploy Docker containers for our production web applications. Each app, backend or frontend, had its own Docker container and was automatically deployed using Circle CI. Mesos would pull from Docker Hub when a new version was released and restart the app with the new version.
Pros
Mesos let us orchestrate containers on our own hardware using our own DNS. We switched from Docker Cloud, which caused several major outages for us.
Cons
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.
Likelihood to Recommend
There's really no reason to ever use Mesos. We switched over to Kubernetes and it's been a breath of fresh air - better CD support, easy CLI for browsing logs, no mysterious dangling redeploys. If you're looking for a tool to manage a fleet of Docker containers on VMs, Kubernetes beats Mesos by a wide margin.
Mesos is being used by some departments and will be used by the whole development and operations team soon. It will be used to improve our pipeline, providing an easy way to deploy containers across our data center. We're using Mesosphere Marathon as a framework to schedule and deploy web applications.
Pros
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.
Cons
The community is good but they are not focusing on web apps deployment. I would like to see the community around Marathon growing.
I would like to have a better support for rkt as a Mesos executor
Likelihood to Recommend
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.