Warning this is a long blog! Full details of this will be available in next week's release of Microservice Deployment, from VirtualPairProgrammers!
This week I have been mainly getting Eureka into production. Specifically, I'm deploying to AWS, in a multi availability-zone configuration. I have an Auto Scaling Group firing up two instances, each in a different Availability Zone (AZ).
This has been, to put it mildly, an "interesting challenge". Obviously Netflix have a massive production load running on it - so we know it works! - but the documentation on how the rest of us should configure it is sketchy at the time of writing.
This blog concentrates on a problem which will be fixed in the forthcoming "Dalston" releases of Spring Cloud, but it may affect those on legacy code bases. (Also Dalston is due for release later in February and I can't delay the course any longer!)