Azure Container Instances vs. D2iQ Mesosphere

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.

Incentivized

• 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

Incentivized

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

Incentivized

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.

Incentivized

• I see mesosphere as having a positive impact overall on the industry trending Docker and containers in general.
• Seeing how mesosphere helps and simplifies things for the developer and ops, it is definitely a game changer.
• Native support of on demand scaling up and down as per the need is one of the best features.

Incentivized