Spring Cloud Eureka High Availability

Record the pits that you tread on.

Spring Cloud Eureka's highly available online tutorials are broadly divided into two categories, one of which is 22 for each other, and the other for three registrations.

1, 22 registration with each other

The registration of ordinary services is http://peer1/eureka/,http://peer2/eureka/this two-car registration has a problem, the Peer1 registry above and Peer2 Registration center above does not have all the services, the rationale is there, But sometimes there is sometimes no, when there is no time, such as the following: There are two services A and b,a on Peer1, B on Peer2, from a through the service name can not find B, so I can not access through the gateway. And then try to change the two registries to write http://peer1/eureka/,http://peer2/eureka/, but still not, still have this situation

2, 3 Registration Center 22 registration

This is a very good way of writing on the Internet, but as in the above situation, there are problems that the service can not be fully synchronized, sometimes back to sync, but after deploying to Docker, there is no synchronization problem, back to cause a series of exceptions

Summarize the functionality of spring cloud but there are some things that are problematic, not that the technology itself is a problem, that it might not be considered when it was designed, that it was the first pit of spring cloud, and that the second big Pit was recorded behind it.

Spring Cloud Eureka High Availability