DC/OS vs Rancher: What are the differences?
DC/OS: The Datacenter Operating System. The easiest way to run microservices, big data, and containers in production. Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications; Rancher: Open Source Platform for Running a Private Container Service. Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
DC/OS belongs to "Cluster Management" category of the tech stack, while Rancher can be primarily classified under "Container Tools".
Some of the features offered by DC/OS are:
- High Resource Utilization
- Mixed Workload Colocation
- Container Orchestration
On the other hand, Rancher provides the following key features:
- Manage Hosts, Deploy Containers, Monitor Resources
- User Management & Collaboration
- Native Docker APIs & Tools
"Easy to setup a HA cluster" is the top reason why over 4 developers like DC/OS, while over 89 developers mention "Easy to use" as the leading cause for choosing Rancher.
DC/OS and Rancher are both open source tools. Rancher with 11.8K GitHub stars and 1.31K forks on GitHub appears to be more popular than DC/OS with 2.16K GitHub stars and 451 GitHub forks.
According to the StackShare community, Rancher has a broader approval, being mentioned in 88 company stacks & 35 developers stacks; compared to DC/OS, which is listed in 19 company stacks and 12 developer stacks.
What is DC/OS?
What is Rancher?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using DC/OS?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
- Consume too much unnecessary resource by just running rancher agent alone;
- Hard to recover from system failure
- Bad performance of load balancing (compare to dokcer swarm built-in LB or others).
The whole infrastructure is managed through Rancher. It provides a simple interface to all the underlying tools - Docker, HAProxy (automatically configures load balancer from the containers).
Currently looking to move to Swarm or Kubernetes due to a few issues I have with Rancher.
Orchestration of containers for our environments. Remote deployment from Jenkins.
We use Rancher for container orchestration and automated deployment pipelines.