--- title: Apache Mesos Reviews meta_title: 'Apache Mesos Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 16 reviews by the users' company size, role or industry to find out how Apache Mesos works for a business like yours. aggregate_rating: rating_value: 4.2 review_count: 16 scale: '5' date_modified: '2026-06-21' parent_category: name: Containerization url: https://www.g2.com/categories/containerization --- # Apache Mesos Reviews **Vendor:** The Apache Software Foundation **Category:** [Container Orchestration Tools](https://www.g2.com/categories/container-orchestration) **Average Rating:** 4.2/5.0 **Total Reviews:** 16 ## About Apache Mesos Apache Mesos is a cluster manager that distributes resources across applications and databases. ## Apache Mesos Reviews ### 1. Handle your cluster as if it were a single machine **Rating:** 4.0/5.0 stars **Reviewed by:** Pablo Francisco P. | Scala/BigData Developer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** November 09, 2017 **What do you like best about Apache Mesos?** I love the abstraction Mesos provides in terms of resource management for cluster. Is seamlessly integrated with Apache Spark. That allow launching Spark tasks in a Mesos cluster by just specifying the Mesos cluster URL. From local to clustered computation in just one parameter. Its C++ code base is quite neat, often using functional programming patterns. **What do you dislike about Apache Mesos?** If you have a distributed application you want to deploy on Mesos, you need to use a framework to handle resource offers for it. That framework is ad-hoc for that application and either someone else wrote it or you need to write it by yourself. However, thanks to Marathon, which acts as a generic framework for containerized applications, you can deploy whichever application you might wrap in a container such as Docker. **What problems is Apache Mesos solving and how is that benefiting you?** Multi-tenant, cluster management. Transparent application deployment. Resource manger for Apache Spark. ### 2. Useful for running many java applications that are long running as well as scheduled **Rating:** 3.5/5.0 stars **Reviewed by:** Gary O. | Lead Software Engineer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** October 24, 2017 **What do you like best about Apache Mesos?** It was easy to set up and get running in a cluster on standard hardware. It also works well in a virtual environment. **What do you dislike about Apache Mesos?** Configuring it properly for memory and cpu usage is tricky. There's also not a lot of software around the cluster management and orchestration. It was hard to get visibility into your running applications. **What problems is Apache Mesos solving and how is that benefiting you?** To be able to fully utilize a cluster of servers and to share the resources so you have little unused capacity. ### 3. Works good for what we were expecting it to do **Rating:** 4.0/5.0 stars **Reviewed by:** Willian M. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** March 13, 2016 **What do you like best about Apache Mesos?** The resource allocation features are the best thing the Mesos has. I like the way we do configuration, it is very simple to run the master and slave process. The idea of extending it with frameworks was really great, now we have some many frameworks to execute a lot of different tasks. **What do you dislike about Apache Mesos?** I don't like to have to use zookeeper to make the master election. It would be better if I could choose the better service discovery service for me. Sometimes is difficult to debug a task with errors. The UI is not so good. It could be better but it works as is. **Recommendations to others considering Apache Mesos:** Choose the right framework for your needs and try it out. There are many good frameworks out there. **What problems is Apache Mesos solving and how is that benefiting you?** We are improving our deployment process by using Mesos + Marathon. The main idea is to reduce our delivery cicle and improve the scalability. ### 4. Experiment **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Internet | Mid-Market (51-1000 emp.) **Reviewed Date:** April 26, 2016 **What do you like best about Apache Mesos?** We are suppose to prepare the necessary execution environments from testing to production and everything in between. Using Docker alongside Mesos allows us to encapsulate execution environments inside the container. In coordination with Mesos it allocates a suitable machine for the service, and deploys it by pulling it from our private Docker hub onto the allocated machine.However, for external software like ElasticSearch we have no need for continuous integration and we release them directly from our local dev environment. To handle this use case we developed Shovel, which we plan to open-source shortly. It automates the process from building the Docker image containing the microservice to finally releasing them to the public. To release a microservice today we only have to prepare a Dockerfile and provide basic configuration. The rest of the release process is then completely handled by Shovel. To further simplify bootstrapping, we have a service template that contains commonly used components and allows us release a new microservice in minutes. **What do you dislike about Apache Mesos?** Mesos is still in its early days, probably best exemplified by the very sub-1.0 version numbers. New Mesos releases often include important bug fixes but upgrading has been a pain point for us due to the number of moving parts that led to catch-22 situations. **Recommendations to others considering Apache Mesos:** I would definitely recommend Apache Mesos to others for its user friendliness **What problems is Apache Mesos solving and how is that benefiting you?** we have no need for continuous integration and we release them directly from our local dev environment. To handle this use case we developed Shovel, which we plan to open-source shortly. It automates the process from building the Docker image containing the microservice to finally releasing them to the public. To release a microservice today we only have to prepare a Dockerfile and provide basic configuration. ### 5. Apache Mesos review **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** April 26, 2016 **What do you like best about Apache Mesos?** In Pre-Mesos we had to prepare the necessary execution environments from testing to production and everything in between. Using Docker alongside Mesos allows us to encapsulate execution environments inside the container. That frees us from the effort of provisioning the infrastructure of every new microservice we want to release. However, for external software like ElasticSearch we have no need for continuous integration and we release them directly from our local dev environment. To handle this use case we developed Shovel, which we plan to open-source shortly. It automates the process from building the Docker image containing the microservice to finally releasing them to the public. To release a microservice today we only have to prepare a Dockerfile and provide basic configuration. The basic configuration includes settings like public URL endpoint or amount of required CPU and memory resources. The rest of the release process is then completely handled by Shovel. To further simplify bootstrapping, we have a service template that contains commonly used components and allows us release a new microservice in minutes. **What do you dislike about Apache Mesos?** Mesos is still in its early days, probably best exemplified by the very sub-1.0 version numbers. New Mesos releases often include important bug fixes but upgrading has been a pain point for us due to the number of moving parts that led to catch-22 situations. As an example, we experienced memory leaks with Docker 1.6 but were not able to upgrade for some time even though the bug got fixed in Docker 1.8. Upgrading Docker would have required upgrading to a Mesos version (0.23) that was untested with Marathon version 0.10. **What problems is Apache Mesos solving and how is that benefiting you?** Financial Applications ### 6. We use Apache Mesos primarily because it is a supported cluster manager for Apache Spark **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** March 17, 2016 **What do you like best about Apache Mesos?** Stability. We rarely encounter problems that are due to Mesos itself. It is nice to be able to simply take down or add machines and have Mesos adjust accordingly. The ability to use frameworks, such as Marathon, on top of it is also key for us. We needed long-running tasks and the ability to invoke them using REST APIs. Support for running tasks within Docker containers is critical for us, so the Docker Containerizer is important. **What do you dislike about Apache Mesos?** Documentation is good enough in most respects, but these days, it should be assumed that some people will want to run the entire Mesos framework within Docker, so officially supported Docker containers out on Docker Hub would help. The mechanism for specifying Mesos configuration options (whether a file exists or not, the name of a file is the option name, and the content is the option value) is odd. First time I've encountered it. **What problems is Apache Mesos solving and how is that benefiting you?** Truthfully, we only use Mesos for some of our Spark related efforts; although we are considering broader uses. These days, we are interested in managing containers more than anything, so we are looking more at Docker Swarm and Kubernetes for management. ### 7. Copied **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Biotechnology | Small-Business (50 or fewer emp.) **Reviewed Date:** March 16, 2016 **What do you like best about Apache Mesos?** Pre-Mesos we had to prepare the necessary execution environments from testing to production and everything in between. Using Docker alongside Mesos allows us to encapsulate execution environments inside the container. That frees us from the effort of provisioning the infrastructure of every new microservice we want to release. Our release process initially consisted of pushing to a service’s git release branch, which automatically triggered the continuous integration process. Marathon serves as deployment manager. In coordination with Mesos it allocates a suitable machine for the service, and deploys it by pulling it from our private Docker hub onto the allocated machine. However, for external software like ElasticSearch we have no need for continuous integration and we release them directly from our local dev environment. To handle this use case we developed Shovel, which we plan to open-source shortly. It automates the process from building the Docker image containing the microservice to finally releasing them to the public. To release a microservice today we only have to prepare a Dockerfile and provide basic configuration. The basic configuration includes settings like public URL endpoint or amount of required CPU and memory resources. The rest of the release process is then completely handled by Shovel. To further simplify bootstrapping, we have a service template that contains commonly used components and allows us release a new microservice in minutes. **What do you dislike about Apache Mesos?** Mesos is still in its early days, probably best exemplified by the very sub-1.0 version numbers. New Mesos releases often include important bug fixes but upgrading has been a pain point for us due to the number of moving parts that led to catch-22 situations. As an example, we experienced memory leaks with Docker 1.6 but were not able to upgrade for some time even though the bug got fixed in Docker 1.8. Upgrading Docker would have required upgrading to a Mesos version (0.23) that was untested with Marathon version 0.10. **What problems is Apache Mesos solving and how is that benefiting you?** Genetics ### 8. I like mesos **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** March 15, 2016 **What do you like best about Apache Mesos?** Mesos is a good tool and I have found it to scale quite well without being in the way. There is also a community around it, and Google's encouragement helps. I can't speak to Mesosphere DCOS because I haven't used it. **What do you dislike about Apache Mesos?** Some aspects of the design can be problematic. Particularly, the way the resource allocation is designed makes it harder to build "intelligent" allocator modules into the mesos master that can decide who to offer resources to. On one hand, fairly simple to write an allocator, but on the other, a custom alllocator can't (last I checked) easily access any data it wants about the current state of the mesos agents and frameworks. Progress is being done in this area, though. **Recommendations to others considering Apache Mesos:** Be skeptical of projects like Kubernetes-Mesos. Use Docker. **What problems is Apache Mesos solving and how is that benefiting you?** I build software and distributed systems to create products. Mesos is a core technology that I've built on top of, so the benefit it provides can perhaps be summarized as "enablement." ### 9. I am a mesos framework developer and operator for a large production mesos cluster. **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** March 15, 2016 **What do you like best about Apache Mesos?** Mesos is great for helping ops teams simplify and condense their infrastructure. The tools is very solid and we have had very few problems with it. There is also a large and growing community of developers creating different frameworks for mesos to suite different needs. We've created our own framework on top of mesos that runs almost the entire product. **What do you dislike about Apache Mesos?** Documentation can be lacking in some cases, making it difficult to get started in certain areas. Getting started on developing a framework, or getting the mesos cluster up and running the first time can be tricky steps. However, other community members or framework developers often have information that can fill in the gaps for these cases. Note: we operate our own mesos cluster and do not use a hosted service **What problems is Apache Mesos solving and how is that benefiting you?** We have mainly used mesos to condense our infrastructure, add stability, and have greater operational simplicity for our ops team. Once we built our own framework on top of it, we were able to take a large amount of the ops-related workload off of developers to allow them to focus on the product itself, which improved the efficiency of many of the teams. ### 10. matured tool for orchestration **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Apache Mesos?** 1. Very good support for docker containers. 2. Easy setup 3. Logging and debug information **What do you dislike about Apache Mesos?** 1. In few occasions mesos-slave becomes non-responsive or stuck phase, there by bunch of tasks queued to it. 2. Very tight integration to Zookeeper. Some times zookeeper is causing memory issues which leads to instability. etcd/consul integration is preferred. **Recommendations to others considering Apache Mesos:** There are so many new orchestration tools available in the market. But Apache mesos is more matured and suits most of the requirements. In the latest versions, docker has provided lots of new features (volume plugins, network plugins), which cannot be leveraged effectively through apache mesos. There are few paid products like nirmata and rancher which are also very competitive and easy to use. If you are using across your enterprise, you can review through the paid products which has many security features like roles, LDAP integration etc.. If yours is very small isolated project, mesos is the best option available currently. **What problems is Apache Mesos solving and how is that benefiting you?** We are managing our APIs under Mesos-Marathon and We are mainly trying to have effective utilization of resources, high availability and on-demand scaling of APIs. Mesos has helped us in managing the multiple servers and workloads effectively. Main benifits we observed are resource aggregation, auto-restart of tasks, simple GUI, multiple frameworks. ### 11. Independent volunteer contributor to Apache Mesos **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Apache Mesos?** Apache Mesos is a cluster management framework. It actually behaves as a kernel for the data center. The best part of Apache Mesos is it's efficient tasks isolation and seamless abstraction of physical resources from VMs or machines or applications. It is going in the right direction and is best suitable for applications like Hadoop, Kafka etc. It also ensures high availability of our applications. It has an easy to use interface also. **What do you dislike about Apache Mesos?** It is a bit heavy as compared to Kubernetes. Also from developer's point of view, it requires a lot of memory to build the source code. **What problems is Apache Mesos solving and how is that benefiting you?** Cluster management having huge scalability and high availability. Very simple to use. ### 12. A Complete Data center kernel **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Telecommunications | Enterprise (> 1000 emp.) **Reviewed Date:** March 16, 2016 **What do you like best about Apache Mesos?** Frame Work APIs and Language Bindings - Lets us provision any types of workload Apache modules - Lets us override most of the functionality or add new functionality without touching the core **What do you dislike about Apache Mesos?** Its completely written C++ , Should be able to add modules written in other programming langs Should be able to distribute it as a single binary (one for master , slave) **What problems is Apache Mesos solving and how is that benefiting you?** Planning to promote Apache Mesos as a centralized resource manager a public cloud. ### 13. I have been working with Mesos to deploy multiple applications accross a computing grid. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** March 15, 2016 **What do you like best about Apache Mesos?** * Fairly straight forward software implementation * API based **What do you dislike about Apache Mesos?** * Schedulers are still fairly immature * Odd marathon issues causes all the jobs to be killed off when trying to fix. **Recommendations to others considering Apache Mesos:** Spend a lot of time putting automation and wrapping the API calls. **What problems is Apache Mesos solving and how is that benefiting you?** We are moving to an architecture where we can quickly change the application mixture quickly and adjust for various traffic patterns and time of day conditions. ### 14. I just tried using Memsos as experimental project ..But it is awesome.. **Rating:** 4.0/5.0 stars **Reviewed by:** Dhyaneshwaran M. | Senior Software Engineer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Apache Mesos?** This takes automation/devops/scalability to next new level . **What do you dislike about Apache Mesos?** Big learning curve .You need to understand the whole system to be able make changes. **What problems is Apache Mesos solving and how is that benefiting you?** More reliable on-demand resizable bigdata cluster . ### 15. Great, works good. **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** March 11, 2016 **What do you like best about Apache Mesos?** Good features. Easy to install. Slaves to master connections work great. **What do you dislike about Apache Mesos?** Frameworks to work with mesos are limited. Simpler UI? Jobs should be auto rescheduled if a slave goes down. **Recommendations to others considering Apache Mesos:** Check out singularity which is a framework that works well with mesos. **What problems is Apache Mesos solving and how is that benefiting you?** Scheduling jobs, tasks etc. Benefits include easy maintenance and monitoring. ### 16. CTO **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Internet | Mid-Market (51-1000 emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Apache Mesos?** Managing the whole DC like one single machine for all distributed system **What do you dislike about Apache Mesos?** Too hard to write executor Not proper for real time system **Recommendations to others considering Apache Mesos:** Ecosystem creation in WW, including more participants ; more focus on APJ **What problems is Apache Mesos solving and how is that benefiting you?** Reducing complexity in DC ## Apache Mesos Discussions - [What is Apache Mesos used for?](https://www.g2.com/discussions/what-is-apache-mesos-used-for) - [View Apache Mesos pricing details and edition comparison](https://www.g2.com/products/apache-mesos/reviews?section=pricing&secure%5Bexpires_at%5D=2026-06-23+22%3A59%3A41+-0500&secure%5Bsession_id%5D=0371b613-cbbd-4cd1-a369-884b251deff5&secure%5Btoken%5D=2c3b998b89261121830e6f61053408041c51e50451ea0149250fd104aab4ebda&format=llm_user) ## Apache Mesos Features **Application Support** - Deployment - Interface support - Processor support - Application Support **System Capability** - Self Healing High Availability - Orchestration - Scalability **Security** - Automatic Security Updates - Security updates ## Top Apache Mesos Alternatives - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - 4.6/5.0 (155 reviews) - [Red Hat OpenShift](https://www.g2.com/products/red-hat-red-hat-openshift/reviews) - 4.5/5.0 (289 reviews) - [Mirantis Kubernetes Engine (formerly Docker Enterprise)](https://www.g2.com/products/mirantis-kubernetes-engine-formerly-docker-enterprise/reviews) - 4.4/5.0 (272 reviews)