D2iQ Mesosphere vs. IBM Cloud Managed Istio

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

Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it. If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.

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

• Layers transparently onto existing applications
• Allows control of access and rules to be developed
• Creates metrics for usage

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

• Some more functionalities added could improve it better.
• Better technical user guidance.

Incentivized

Training and usage support available

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

• It reduced the complexity of network mesh (ingress/egress services).
• One tool with many solutions. No need to integrate monitoring tools or notification tools.
• It reduced the number of lines of YAML code.
• It reduced the number of labor hours.

Incentivized