Apache Mesos

(16)
4.2 out of 5 stars

Apache Mesos is a cluster manager that distributes resources across applications and databases.

Work for Apache Mesos?

Learning about Mesos?

We can help you find the solution that fits you best.

Apache Mesos Reviews

Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 16 Mesos reviews
LinkedIn Connections
Mesos review by <span>Pablo Francisco P.</span>
Pablo Francisco P.
Validated Reviewer
Review Source

"Handle your cluster as if it were a single machine"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

Multi-tenant, cluster management. Transparent application deployment. Resource manger for Apache Spark.

Sign in to G2 Crowd to see what your connections have to say about Apache Mesos
Mesos review by <span>Willian M.</span>
Willian M.
Validated Reviewer
Verified Current User
Review Source

"Works good for what we were expecting it to do"

What do you like best?

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?

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 the product

Choose the right framework for your needs and try it out. There are many good frameworks out there.

What business problems are you solving with the product? What benefits have you realized?

We are improving our deployment process by using Mesos + Marathon. The main idea is to reduce our delivery cicle and improve the scalability.

What Container Orchestration solution do you use?

Thanks for letting us know!
Mesos review by Industry Analyst / Tech Writer in Internet
Industry Analyst / Tech Writer in Internet
Validated Reviewer
Verified Current User
Review Source

"Experiment"

What do you like best?

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?

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 the product

I would definitely recommend Apache Mesos to others for its user friendliness

What business problems are you solving with the product? What benefits have you realized?

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.

Mesos review by Industry Analyst / Tech Writer in Information Technology and Services
Industry Analyst / Tech Writer in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Apache Mesos review"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

Financial Applications

Mesos review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"We use Apache Mesos primarily because it is a supported cluster manager for Apache Spark"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Mesos review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"Copied"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

Genetics

Mesos review by User in Computer Software
User in Computer Software
Validated Reviewer
Verified Current User
Review Source

"I like mesos"

What do you like best?

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?

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 the product

Be skeptical of projects like Kubernetes-Mesos.

Use Docker.

What business problems are you solving with the product? What benefits have you realized?

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."

Mesos review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"I am a mesos framework developer and operator for a large production mesos cluster."

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

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.

Mesos review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source

"matured tool for orchestration"

What do you like best?

1. Very good support for docker containers.

2. Easy setup

3. Logging and debug information

What do you dislike?

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 the product

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 business problems are you solving with the product? What benefits have you realized?

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.

Mesos review by <span>Gary O.</span>
Gary O.
Validated Reviewer
Review Source

"Useful for running many java applications that are long running as well as scheduled"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

To be able to fully utilize a cluster of servers and to share the resources so you have little unused capacity.

Mesos review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"Independent volunteer contributor to Apache Mesos"

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

Cluster management having huge scalability and high availability. Very simple to use.

Mesos review by User in Telecommunications
User in Telecommunications
Validated Reviewer
Verified Current User
Review Source

"A Complete Data center kernel "

What do you like best?

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?

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 business problems are you solving with the product? What benefits have you realized?

Planning to promote Apache Mesos as a centralized resource manager a public cloud.

Mesos review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source

"I have been working with Mesos to deploy multiple applications accross a computing grid."

What do you like best?

* Fairly straight forward software implementation

* API based

What do you dislike?

* Schedulers are still fairly immature

* Odd marathon issues causes all the jobs to be killed off when trying to fix.

Recommendations to others considering the product

Spend a lot of time putting automation and wrapping the API calls.

What business problems are you solving with the product? What benefits have you realized?

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.

Mesos review by <span>Dhyaneshwaran M.</span>
Dhyaneshwaran M.
Validated Reviewer
Verified Current User
Review Source

"I just tried using Memsos as experimental project ..But it is awesome.."

What do you like best?

This takes automation/devops/scalability to next new level .

What do you dislike?

Big learning curve .You need to understand the whole system to be able make changes.

What business problems are you solving with the product? What benefits have you realized?

More reliable on-demand resizable bigdata cluster .

Mesos review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Great, works good. "

What do you like best?

Good features. Easy to install. Slaves to master connections work great.

What do you dislike?

Frameworks to work with mesos are limited. Simpler UI? Jobs should be auto rescheduled if a slave goes down.

Recommendations to others considering the product

Check out singularity which is a framework that works well with mesos.

What business problems are you solving with the product? What benefits have you realized?

Scheduling jobs, tasks etc.

Benefits include easy maintenance and monitoring.

Mesos review by Consultant in Internet
Consultant in Internet
Validated Reviewer
Verified Current User
Review Source

"CTO"

What do you like best?

Managing the whole DC like one single machine for all distributed system

What do you dislike?

Too hard to write executor

Not proper for real time system

Recommendations to others considering the product

Ecosystem creation in WW, including more participants ; more focus on APJ

What business problems are you solving with the product? What benefits have you realized?

Reducing complexity in DC

Kate from G2 Crowd

Learning about Apache Mesos?

I can help.
* We monitor all Apache Mesos reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.