Item: Mirantis Kubernetes Engine
Rating: 7
Author: Verified User

Overall Satisfaction with Docker

Use Cases and Deployment Scope

We use Swarm to deploy internal applications in a managed cluster. These applications are mission-critical and used across all departments in the organization. Swarm solves the problem of scaling and load balancing traffic and resources during peak business hours. It allows fast and simple automated deployment which drastically reduces the time spent on this task by developers.

Pros and Cons

Pros

Managing a cluster of micro-services.
Redundancy, fault-tolerance, and load balancing.

Cons

Small community - not a lot of information available outside of the documentation.
Logging - centralized logging for all applications is something we wish was available.

Return on Investment

Our deployment process for multiple micro-services has gone down from roughly 3 hours to 20 minutes with centralized orchestration.
Replaced multiple tools for deployment and load balancing with just Swarm.

Key Insights

Do you think Mirantis Kubernetes Engine delivers good value for the price?

Yes

Are you happy with Mirantis Kubernetes Engine's feature set?

Yes

Did Mirantis Kubernetes Engine live up to sales and marketing promises?

Yes

Did implementation of Mirantis Kubernetes Engine go as expected?

Yes

Would you buy Mirantis Kubernetes Engine again?

Yes

Other Software Used

NGINX, Dokku

Likelihood to Recommend

Swarm is well suited to deploy in an infrastructure of distributed micro-services and orchestrating them from a central platform. It does this job very well, and if you're looking for this functionality, I highly recommend Swarm. However, if you're simply looking for a load balancing and horizontal scaling, I think there are far better and even simpler tools available more suited to that task.

Docker Swarm: Simplify Multiple Deployments