D2iQ (formerly Mesosphere) still supports the Mesosphere solution, which is designed for operations at a very large scale. It's powered by DC/OS, a production-proven cloud native platform that runs containers and data services on the same infrastructure.
D2iQ rebranded to reflect their change and broadening of focus towards Kubernetes but other services such as Cassandra, Kafka, and Spark. D2iQ also now offers IT professional services in tandem with its products.
N/A
Pricing
D2iQ Mesosphere
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
D2iQ Mesosphere
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
D2iQ Mesosphere
Considered Both Products
D2iQ Mesosphere
Verified User
Manager
Chose D2iQ Mesosphere
Mesosphere vs. ECS Mesosphere has a direct competition with companies using AWS Cloud, as the ECS product is one of the closest competitors to Mesosphere. Mesosphere has an edge with simplistic hosting and deep and easy integration with Jenkins Pipelines and native plugins …
I happen to like mesosphere because it integrates well with a Jenkins based workflow, Deis is a little more Heroku like and it's not clear how to fit that model into a continuous-integration process. Kubernetes has also been criticized for being complicated.
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.
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.
I happen to like mesosphere because it integrates well with a Jenkins based workflow, Deis is a little more Heroku like and it's not clear how to fit that model into a continuous-integration process. Kubernetes has also been criticized for being complicated.