D2iQ Mesosphere vs. Google Kubernetes Engine vs. Mirantis Kubernetes Engine

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

If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.

Incentivized

[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs
and separates any single application from the dependencies. Also, this tool is
helping me in the agile development of the processes. It is strongly recommended to
almost all major organizations.

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

• Engine upgrade rollout strategy - well documented and configurable
• Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
• Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)

Incentivized

• Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
• Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
• CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.

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

• Support of IPv6.
• Better GitOps.
• A "serverless" Kubernetes so we can install Google config connector will be really awesome.
• Container-native load balancers do not support internal TCP/UDP load balancers or network load balancers.

Incentivized

• Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
• Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
• Networking is complexified due to internal port mapping between containers, etc.

Incentivized

• Google Kubernetes Engine has a good UI and documentation that facilitates setup and helps get projects moving along quickly
• Its built-in logging integrations with StackDriver make it easier to monitor the application and log issues quickly
• Automated orchestration, deployment, and scaling of nodes and networking are all easily configurable with yaml files

Incentivized

Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.

Incentivized

Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.

Incentivized

The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.

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

GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.

Incentivized

We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.

Incentivized

• When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.

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

• Reduced cloud computing costs.
• Easier management of applications.
• Extra time investment to learn how to setup applications in Google versus Amazon.

Incentivized

• Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
• Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
• Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.

Incentivized