Why Zookeeper’s CP Model Fails as a Service Registry

Why Zookeeper’s CP Model Is Unsuitable for Service Registries

Zookeeper is a mature distributed coordination system, but its CP nature makes it a poor choice for service discovery where availability is paramount.

CAP Implications

In the CAP model Zookeeper is CP, meaning it sacrifices availability during network partitions to preserve consistency. For a coordination service this is correct, but for a service registry an AP (eventual consistency) approach is preferable.

The registry essentially provides a query function: ServiceList = F(service-name) Given a service-name, it returns a list of available endpoints ip:port.

Impact of Inconsistent Service Lists

If different clients receive inconsistent lists, traffic becomes unevenly distributed across instances.

s1 = { ip1, ip2, …, ip9 }
s2 = { ip2, ip3, …, ip10 }

This leads to some instances receiving a single request while others receive duplicate traffic, but the imbalance is tolerable and temporary.

Consequences of CP‑Induced Unavailability

During a network partition, Zookeeper’s leader election can render a minority partition unavailable, causing the entire registry to become inaccessible even for services within the same data center.

Performance Limitations

Zookeeper’s write operations are handled only by the leader, creating a bottleneck in large‑scale service registration scenarios. The leader cannot be horizontally scaled, and persistent long‑lived connections add further load.

Each write generates a transaction log and periodic memory dumps to disk, which degrades performance—unnecessary for a registry.

Conclusion

Zookeeper’s CP consistency guarantees are mismatched with the high‑availability requirements of a service registry, and its performance characteristics do not scale to massive registration workloads. An AP‑oriented registry is more appropriate.

References:

http://jm.taobao.org/2018/06/13/%E5%81%9A%E6%9C%8D%E5%8A%A1%E5%8F%91%E7%8E%B0%EF%BC%9F/

https://medium.com/knerd/eureka-why-you-shouldnt-use-zookeeper-for-service-discovery-4932c5c7e764