These are chat archives for spring-cloud/spring-cloud
@bsushant-athena I think it has more todo with how the eureka services works internally. It will try to find the 'closest' one by default. Which means the one in the same availability zone. Beyond this fact, how many eureka servers you want to have if up to you. I would minium 2. From some guidelines 3 (you are doing maintenance on 1, 1 goes down and you are still up) you should not be bothered where the machines run. For example i made it using the elastic-ip. I defined 1 elastic-ip for each zone. If a AWS zone would go down, the server could not bootup anymore in that zone, but will then take a non-allocated ip from the whole range (3) and boot up in another zone, so you will still end up with 3 eureka servers. The same would happen for any microservice that was running the zone that went done. It will be booted up in another zone.
As a general notice. Try to avoid using internal load balancers between microservies as it counters the effect of using the discovery service.