Flocker vs Rancher: What are the differences?
Developers describe Flocker as "Run your databases in Docker and make them as portable as the rest of your app". Flocker is a data volume manager and multi-host Docker cluster management tool. With it you can control your data using the same tools you use for your stateless applications. This means that you can run your databases, queues and key-value stores in Docker and move them around as easily as the rest of your app. On the other hand, Rancher is detailed as "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.
Flocker and Rancher can be primarily classified as "Container" tools.
"Open-Source" is the top reason why over 3 developers like Flocker, while over 89 developers mention "Easy to use" as the leading cause for choosing Rancher.
Flocker and Rancher are both open source tools. It seems that Rancher with 11.8K GitHub stars and 1.31K forks on GitHub has more adoption than Flocker with 3.18K GitHub stars and 287 GitHub forks.
What is Flocker?
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 Flocker?
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.
We use Rancher for container orchestration and automated deployment pipelines.