Likelihood to Recommend
There's really no reason to ever use Mesos. We switched over to
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,
beats Mesos by a wide margin.
Read full review
Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it. If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.
Read full review 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. Read full review Layers transparently onto existing applications Allows control of access and rules to be developed Creates metrics for usage Read full review 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. Read full review Some more functionalities added could improve it better. Better technical user guidance. Read full review Support Rating
No real support channel, the Mesos
issues list was the only one we found and it wasn't particularly helpful.
Read full review
Training and usage support available
Read full review Alternatives Considered Kubernetes
is really great and their community is growing really fast (Google influence). We evaluated it in the beginning and it would fit for our web applications workload. We decided to proceed with Mesos because it has more potential. You may use a different framework for different kinds of tasks on Mesos. There is a
framework for Mesos, by the way.
Read full review Read full review Return on Investment It's optimizing our resources. It's improving our process. This argument is not just for Mesos, but we needed a tool like this to start changing and it works like a charm. It's open source. Read full review It reduced the complexity of network mesh (ingress/egress services). One tool with many solutions. No need to integrate monitoring tools or notification tools. It reduced the number of lines of YAML code. It reduced the number of labor hours. Read full review