Traefik vs Zookeeper: What are the differences?
Traefik: Load Balancer for Microservices. Træfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker, Swarm, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file...) to manage its configuration automatically and dynamically; Zookeeper: Because coordinating distributed systems is a Zoo. A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.
Traefik and Zookeeper are primarily classified as "Load Balancer / Reverse Proxy" and "Open Source Service Discovery" tools respectively.
"Kubernetes integration" is the top reason why over 10 developers like Traefik, while over 9 developers mention "High performance ,easy to generate node specific config" as the leading cause for choosing Zookeeper.
Traefik is an open source tool with 23K GitHub stars and 2.36K GitHub forks. Here's a link to Traefik's open source repository on GitHub.
Uber Technologies, Pinterest, and Coursera are some of the popular companies that use Zookeeper, whereas Traefik is used by Docplanner, Viadeo, and Condé Nast. Zookeeper has a broader approval, being mentioned in 116 company stacks & 48 developers stacks; compared to Traefik, which is listed in 46 company stacks and 17 developer stacks.
What is Traefik?
What is Zookeeper?
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 Zookeeper?
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
Initially, Stitch only supported real-time updates and addressed this problem with a MapReduce job named The Restorator that performed the following actions:
- Calculated the expected totals
- Queried Cassandra to get the values it had for each counter
- Calculated the increments needed to apply to fix the counters
- Applied the increments
Meanwhile, to stop the sand shifting under its feet, The Restorator needed to coordinate a locking system between itself and the real-time processors, so that the processors did not try to simultaneously apply increments to the same counter, resulting in a race-condition. It used ZooKeeper for this.
Like many large scale web sites, Pinterest’s infrastructure consists of servers that communicate with backend services composed of a number of individual servers for managing load and fault tolerance. Ideally, we’d like the configuration to reflect only the active hosts, so clients don’t need to deal with bad hosts as often. ZooKeeper provides a well known pattern to solve this problem.
Zookeeper manages our state, and tells each node what version of code it should be running.
Used Zookeeper as the resource management system for Mesos/Marathon services.