Springcloudconfig and Springcloudeureka registry and configuration Center high availability

All configurations are cached locally, the remote Configuration center down, without affecting local use, but cannot be re-requested by the server to obtain the configured updates.

Whether it's high availability in the registry, or high availability in the configuration center.
Essentially, the service is guaranteed to be registered or can be obtained from the configuration center.

The high availability of the registry means that if there is a registration center down, other registries can also provide registration and enquiry services,
Even if all registry servers are fully down, it does not affect the use of providers and consumers, since the first time a service consumer requests a registration center,
Caches the provider's address locally, and also directly invokes the service provided by the provider (the service provider can deploy multiple machines, and consumers can use the feign and ribbon. To perform load balancing operations. ）

High availability of the configuration center Similarly, it is only guaranteed that when I update the configuration, the configuration client can reconnect to the configuration server for the update operation.

Springcloudconfig and Springcloudeureka registry and configuration Center high availability