Dubbo ZooKeeper Registry Implementation Principle Analysis

This article provides an in-depth analysis of the ZooKeeper registry implementation in Dubbo (ZooKeeperRegistry) by examining its inheritance hierarchy from top to bottom.

The analysis covers four key classes:

AbstractRegistry provides local caching of service data in memory, synchronized with disk files. It uses a Properties object for in-memory storage and a File object for persistent storage, with the file.cache parameter controlling whether caching is enabled.

FailbackRegistry handles exception retry logic for registry operations using a timing wheel (HashedWheelTimer). It overrides five core methods (register/unregister, subscribe/unsubscribe, notify) and uses a template method pattern, delegating actual logic to subclasses while managing retry operations through the timing wheel.

CacheableFailbackRegistry introduces optimizations for the URL push model in Dubbo 3.0. It separates URL into URLAddress (containing host, port) and URLParam (containing parameters), enabling multi-level caching to reduce URL object creation. This significantly improves performance when dealing with large numbers of service providers during scaling operations.

ZooKeeperRegistry provides the actual ZooKeeper-based registry implementation. Service providers register as ephemeral nodes when starting, while consumers subscribe to service data and register Watcher listeners. When service provider instances change (scale up/down), ZooKeeper notifies consumers through the Watcher mechanism, enabling dynamic service discovery.

The article also explains ZooKeeper fundamentals including its tree-structured data model, node types (persistent and ephemeral), Watcher mechanism characteristics (active push, one-time trigger, visibility, ordering), and session management with heartbeat detection.