TrustRadius Insights for D2iQ Mesosphere are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Effortless Cluster Setup: Several users have praised the platform for its ability to easily spin up clusters using industry-standard tools within minutes. This has allowed them to have a centralized dashboard and logging capability for all their managed k8s clusters without any configuration, saving them valuable time and effort.
Seamless Integration with Existing Workflows: Reviewers appreciate that once installed, they can communicate with their clusters the same way they are used to, using kubectl. This seamless integration with existing workflows is a standout feature for many users, allowing for a smooth transition and minimizing disruption.
Efficient Resource Management: Many users find the support for several frameworks for scheduling different kinds of workloads and the 2-level scheduling system highly efficient in managing resources. They feel that this results in great efficiency and helps streamline their workload management processes.
I have used Mesosphere for orchestrating Docker Container workloads. The main feature that mesosphere provides is cloud agnostic capabilities and it can be used across multiple cloud providers or within a hybrid scenario where you have a fusion between your own data centers and the cloud. Mesosphere as a product is being used by my team for managing and provisioning Docker Container workloads.
Pros
Cloud Agnostic
Simple to Use
Simplistic UI
Easy to Operate and Scale
Cons
Setting up is a bit of a hassle, especially ZooKeeper state management and mesos and marathon quorum.
Occasionally, I observed some failures when deploying something onto Marathon. Logging or detailed error reporting can help.
Stale containers and inconsistent states resultant of the cluster failure are hard to solve and need a complete system restart to get it back to normal state.
Likelihood to Recommend
Mesosphere is well suited for orchestrating workloads. It supports Docker as a container as well as support others. It is highly suitable for running resilient and auto recovering big data/application containers. Mesosphere has proven time and again to be production ready at a massive scale. It supports native single button/API call scale up and scale down and supports various deployment patterns like Blue-Green and others.
I personally straddle the line between dev-ops and development, and I think mesosphere and friends adds value to both of those roles. From the dev-ops perspective using a mesosphere foundation allows for applications to be treated in a uniform way, and deployed in an efficient manner across a cluster. It's also easy to scale out. From a development perspective it puts a certain amount of dev-ops power in my hands which I would otherwise have to rely on dev-ops to do (e.g. install a particular version of node.js on these servers). It's a win-win all around. There are some issues in terms of the dev org, deploying things that the dev-ops org isn't fully up to snuff on support, so this aspect is the main challenge in my mind around the docker/scheduler paradigm. What mesosphere brings to the table is a packaged deployment solution for mesosphere and "frameworks" that facilitate deployment of various applications onto the mesosphere grid. Deploying mesosphere and various applications on top of it can be non trivial, so Mesosphere datacenter operating system (DCOS) can help a great deal with that.
Pros
Deploying mesosphere and friends (e.g. marathon)
Deploying applications (e.g. Cassandra, Jenkins, Spark) on to mesosphere
Providing value add components such as velocity, and marathon-lb
Cons
There isn't any specific support for upgrading (DCOS) when running in AWS. You basically have to create a new vpc and figure out how to get all your Marathon jobs from the old instance to the new instance. I think some kind of a backup/restore operation against Marathon could be helpful there.
Occasionally, I will experience silent failures when deploying something onto Marathon. I think an easier way to track down failures would be helpful.
There are some features that are reserved for the licensed enterprise offering, but in some cases, I think the feature (e.g. security) is fundamental, and it may lead to the tech being avoided because it doesn't have enough momentum to get the customer hooked. I would like to see more features provided with the open-source version and reserve licensing for support.
Likelihood to Recommend
I think right now Mesosphere is newer to Windows environments and has some challenges with stepping in to big data scenarios where YARN is currently being used.
VU
Verified User
Technician in Information Technology (201-500 employees)