apache/zookeeper
Apache ZooKeeper observed · 2026-08-28
Health v2 · maintenance only
77/100
- Activity 99
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 6368
- days_rel: n/a
- days_push: 8
- n_releases_24m: 0
Adoption not part of the score
12795 stars · 7330 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Apache ZooKeeper is a high-performance, fault-tolerant coordination service for distributed applications, exposing a hierarchical key-value namespace with ordered, replicated updates via the ZAB consensus protocol. It provides off-the-shelf primitives such as naming, configuration management, synchronization, and group services used by systems like Kafka, Hadoop, and HBase.
Use cases
- implement leader election among distributed workers
- build distributed locks and mutexes across a cluster
- register and discover live service instances dynamically
- propagate configuration changes to all nodes with watches
- track cluster membership and node liveness in real time
- synchronize phased computations with barriers and queues
- store small amounts of strongly consistent metadata for a distributed system
When to choose
- you need battle-tested coordination primitives (locks, leader election, group membership) with strong consistency
- you operate distributed systems like Kafka, Hadoop, or HBase that depend on ZooKeeper
- you need a small, highly reliable replicated key-value store with total ordering of updates
- you want watches to push configuration changes without polling
When to avoid
- you need to store large volumes of data or serve as a general-purpose database
- you want a modern consensus store with a richer API like etcd or Consul
- your workload requires horizontal write scaling rather than a single coordinated quorum
- you only need simple caching or messaging without coordination guarantees
Facets
service · maturity stable
database service-discovery configuration-management caching message-queue microservices databases infrastructure-as-code backend jvm windows cross-platform self-hosted coordination consensus zab leader-election distributed-locks key-value-store apache cluster-management devops linux macos docker
6 sources
- readme: https://github.com/apache/zookeeper · fetched 2026-08-28 · 50623b235264
- homepage: https://zookeeper.apache.org · fetched 2026-08-29 · 0768e26c6a5f
- site_page: https://zookeeper.apache.org/releases · fetched 2026-08-29 · 3a537c94c329
- site_page: https://zookeeper.apache.org/doc/r3.9.5 · fetched 2026-08-29 · b4db9ee39ab6
- site_page: https://zookeeper.apache.org/doc/r3.8.6 · fetched 2026-08-29 · 230f9cf3cf36
- site_page: https://zookeeper.apache.org/doc/r3.7.2 · fetched 2026-08-29 · b103e2f29246
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| apache/zookeeper | main | 77 |
For agents
markdown · JSON · MCP: product_card(name="apache/zookeeper")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem