DickChesterwood
commented
6 years ago API Gateway:
Now always runs on the standard port 8080. Normally we don't allow hardcodes of ports but this one exception is different - clients outside the MS Estate need to connect to a known port.
standalone - n/a local-microservice - connects to position tracker on port 8081 production-microservice - uses k8s DNS to find position tracker (and others of course)
Both versions use the feign and hystrix support (configured in the cloud configuration class)
Position Tracker
standalone - generates its own messages on a local embedded queue. local-microservice - connects to ApacheMQ running locally production-microservice - k8s DNS
Position Simulator
standalone - doesn't make much sense local-microservice - ApacheMQ running locally production-microservice - as usual k8s DNS
standalone - run alone, always development. Needs no other external dependency. local-microservice - run locally but as a microservice architecture production-microservice - the full stack as deployed to live hardware with k8s