Compare Apache Mesos and Kubernetes 
- Users report that Kubernetes excels in orchestration capabilities, with a score of 9.6, while Apache Mesos trails behind with a lower score, indicating that Kubernetes provides a more robust framework for managing containerized applications effectively.
- Reviewers mention that Kubernetes offers superior scalability, which is crucial for enterprises looking to grow their applications seamlessly. In contrast, Apache Mesos, while capable, does not match the same level of scalability as Kubernetes.
- G2 users highlight Kubernetes' strong access control features, scoring 8.7, which enhances security and user management. Users on G2 note that Apache Mesos, while functional, does not provide the same level of granularity in access control.
- Users say that Kubernetes has a more user-friendly interface, contributing to its ease of use score of 7.8, compared to Apache Mesos' score of 7.4. This difference can significantly impact the onboarding process for new users.
- Reviewers mention that Kubernetes has a more active community and better support, reflected in its quality of support score of 8.4, compared to Apache Mesos' 7.8. This can be a deciding factor for organizations that rely on community resources and support.
- Users report that Kubernetes' self-healing capabilities are a standout feature, allowing for automatic recovery from failures, which is essential for maintaining high availability. Apache Mesos, while it has some self-healing features, does not match the effectiveness of Kubernetes in this area.
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.
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...
Kubernetes is a sweet spot between flexibility and simplicity. Especially service discovery is made very simple. Competitors often are either to simple (Docker compose, swarm, fleet) or too complex (Marathon). Once it is up and running, low-level...
It's extremely immature (very buggy), the networking is just...painful, the scheduler is dumb and slow; those are my technical dislikes. My personal dislike is the overall lack of cohesive documentation as well as the assertion that just because there...
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.
Kubernetes is a sweet spot between flexibility and simplicity. Especially service discovery is made very simple. Competitors often are either to simple (Docker compose, swarm, fleet) or too complex (Marathon). Once it is up and running, low-level...
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...
It's extremely immature (very buggy), the networking is just...painful, the scheduler is dumb and slow; those are my technical dislikes. My personal dislike is the overall lack of cohesive documentation as well as the assertion that just because there...
![Yiorgos [George] A.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Yiorgos [George] A.")
