Can Dubbo Services Still Be Invoked When the Registry Goes Down?

Can Dubbo Services Still Be Invoked After the Registry Goes Down?

The answer is yes. When Dubbo starts, consumers pull provider interface data from the registry and cache it locally; subsequent calls use the cached addresses.

If a single node in a registry cluster fails, the system automatically switches to another node. If the entire registry becomes unavailable, providers and consumers can still communicate using the local cache.

Robustness

The monitoring center failure does not affect usage, only some sampling data is lost.

If the database fails, the registry can still provide service‑list queries from cache, but new services cannot be registered.

In a registry cluster, any single node failure triggers automatic failover to another node.

When the entire registry is down, providers and consumers continue communication via local cache.

Service providers are stateless; any single provider failure does not affect usage.

If all service providers go down, consumer applications cannot use the service and will keep attempting reconnection until providers recover.

Reference: Dubbo official documentation.

http://dubbo.apache.org/zh-cn/docs/user/preface/architecture.html