Eurake partition understanding

Hello everyone , I meet you again , I'm your friend, Quan Jun .

Eurake Partition understanding If there are multiple machine rooms in large projects , For example, Beijing computer room , Shanghai computer room , Hangzhou machine room , Thousands of services are registered in Eurake above , Our examples are also deployed in various regions . Now , Because there are different areas in the machine room , If a service in Beijing calls a service in Shanghai , Delay may occur , The response speed of the service will also be much slower , Now , We may expect , Beijing's service producers use Beijing's services to consume , How to operate this ？ Eurake In fact, there is a partition function , What is partition , There is a registration center in Beijing , Shanghai , Hangzhou also has , Here we need to mention a configuration eureka.instance.region, You can set up multiple registration centers , In different computer rooms , Each machine room can have multiple services , stay eureka.instance.availability-zones, Set up different computer room areas in Beijing , Last in service-url Registered address , How to set which registered address to get the service instance from , One configuration is prefer-same-zone-eureka, If it is true, From availability-zones The first area to register , If registration fails , Then continue to register with other services , If the registration fails three times , Try again after a heartbeat If prefer-same-zone-eureka yes false, He will service-uri Take one list, Register from the first , If the registration is successful , Keep your heart beating , If you fail , Then continue to take it down .

Publisher ： Full stack programmer stack length , Reprint please indicate the source ：https://javaforall.cn/131505.html Link to the original text ：https://javaforall.cn