How does Dubbo work? Can I continue communication when the registry is down?

Step 1: The provider registers with the registry. Step 2: The consumer subscribes to the service from the registry, and the registry notifies the consumer of the registered service. Step 3: The consumer invokes the Provider. Both the consumer and provider notify the monitoring center asynchronously

Service registration and discovery 1. Bind the Provider to the specified port and start the service. 2. Connect the Provider to the registry and send the local IP, port, application information and service information to the registry storage. 4. According to the service information requested by consumers, the registry matches the corresponding provider list and sends it to the Consumer application cache. 5. When making a remote call, the Consumer makes the call based on one of the cached Consumer lists. 6. Provider status changes will be notified to the registry in real time and pushed to the Consumer by the registry in real time. Registry for itself can be a peer cluster, but the dynamic increase or decrease in node, and after a crash, will automatically switch to another 7, decentralization, the two sides are not directly in accordance with the lazy registry, if the registry all down in a short period of time will not affect the service call 8 stateless, service providers, arbitrary after a crash, does not affect use

Can I continue communication when the registry is down? Yes, because at initial initialization, the consumer pulls the provider’s address and other information into the local cache, so communication can continue when the registry is down.