Apache Mesos

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Mesos
Score 2.6 out of 10
N/A
N/AN/A
Pricing
Apache Mesos
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
Mesos
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup FeeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache Mesos
Considered Both Products
Mesos
Chose Apache Mesos
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.
Chose Apache Mesos
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 …
Top Pros
Top Cons
Best Alternatives
Apache Mesos
Small Businesses
Portainer
Portainer
Score 9.3 out of 10
Medium-sized Companies
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.2 out of 10
Enterprises
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.2 out of 10
All AlternativesView all alternatives
User Ratings
Apache Mesos
Likelihood to Recommend
2.0
(2 ratings)
Support Rating
1.0
(1 ratings)
User Testimonials
Apache Mesos
Likelihood to Recommend
Apache
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.
Read full review
Pros
Apache
  • 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
Cons
Apache
  • 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
Support Rating
Apache
No real support channel, the Mesos GitHub issues list was the only one we found and it wasn't particularly helpful.
Read full review
Alternatives Considered
Apache
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 Kubernetes framework for Mesos, by the way.
Read full review
Return on Investment
Apache
  • 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
ScreenShots