Top-bewertete Apache Mesos Alternativen
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. Bewertung gesammelt von und auf G2.com gehostet.
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 Bewertung gesammelt von und auf G2.com gehostet.
15 von 16 Gesamtbewertungen für Apache Mesos
Gesamtbewertungsstimmung für Apache Mesos
Melden Sie sich an, um die Bewertungsstimmung zu sehen.
Ich liebe die Abstraktion, die Mesos in Bezug auf Ressourcenmanagement für Cluster bietet. Es ist nahtlos in Apache Spark integriert. Das ermöglicht das Starten von Spark-Aufgaben in einem Mesos-Cluster, indem einfach die Mesos-Cluster-URL angegeben wird. Von lokaler zu verteilter Berechnung mit nur einem Parameter.
Sein C++-Code ist ziemlich sauber und verwendet oft funktionale Programmiermuster. Bewertung gesammelt von und auf G2.com gehostet.
Wenn Sie eine verteilte Anwendung haben, die Sie auf Mesos bereitstellen möchten, müssen Sie ein Framework verwenden, um Ressourcenangebote dafür zu verwalten. Dieses Framework ist ad-hoc für diese Anwendung und wurde entweder von jemand anderem geschrieben oder Sie müssen es selbst schreiben. Dank Marathon, das als generisches Framework für containerisierte Anwendungen fungiert, können Sie jedoch jede Anwendung bereitstellen, die Sie in einen Container wie Docker einpacken. Bewertung gesammelt von und auf G2.com gehostet.
Es war einfach, es auf Standard-Hardware in einem Cluster einzurichten und zum Laufen zu bringen. Es funktioniert auch gut in einer virtuellen Umgebung. Bewertung gesammelt von und auf G2.com gehostet.
Es ist schwierig, es richtig für Speicher- und CPU-Nutzung zu konfigurieren. Es gibt auch nicht viel Software für das Cluster-Management und die Orchestrierung. Es war schwer, Einblick in Ihre laufenden Anwendungen zu bekommen. Bewertung gesammelt von und auf G2.com gehostet.
Die Ressourcenallokierungsfunktionen sind das Beste, was Mesos hat. Ich mag die Art und Weise, wie wir die Konfiguration durchführen, es ist sehr einfach, den Master- und Slave-Prozess auszuführen. Die Idee, es mit Frameworks zu erweitern, war wirklich großartig, jetzt haben wir viele Frameworks, um viele verschiedene Aufgaben auszuführen. Bewertung gesammelt von und auf G2.com gehostet.
Ich mag es nicht, Zookeeper für die Master-Wahl verwenden zu müssen. Es wäre besser, wenn ich den besseren Service-Discovery-Dienst für mich wählen könnte.
Manchmal ist es schwierig, eine Aufgabe mit Fehlern zu debuggen. Die Benutzeroberfläche ist nicht so gut. Sie könnte besser sein, aber sie funktioniert so, wie sie ist. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
1. Very good support for docker containers.
2. Easy setup
3. Logging and debug information Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
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. Bewertung gesammelt von und auf G2.com gehostet.
