Here i am giving you demo of ideal microservice architecture with running sample code.
* Edge Services - Gateway -> ZUUL
* Service Registry -> ServiceRegistry -> Eureka
* Configuration -> Config -> Cloud Configuration.
* Rest Apis -> MS1,MS2 -> Spring rest apis
# Currently , i am using ZUUL , once Spring cloud gateway get stable we move to that.
# Gateway pointing to ServiceRegistry to discover the new microService in the environment
# Gateway also point to Config to get the dynamic routing
# Independent Service , i am using eureka here to manage registry.
# Independent Service
# The thing which are missing in this currently , git monitoring webhook will deploy it soon.
# Currently config reading from ~/tmp/config git directory
# Simple MicroService with 2 api /v1/ & /message
# Registered with Eureka
# pointing to cloud for fetching configuration
# Zipkin enable for tracing, in log you can check track id & span id
# Simple MicroService with 1 api /v1/
# Registered with Eureka
# pointing to cloud for fetching configuration
# Zipkin enable for tracing, in log you can check track id & span id
# In each microservice sleuth is enable which help in tracing the request
# and Zipkin Server is running on one instance and all microservice & gateway pointing to zipkin base url.
I have enable docker for easy deployment and maintainence. You can find the above docker images : https://hub.docker.com/u/ritreshgirdhar/ https://store.docker.com/community/images/ritreshgirdhar/serviceregistry https://store.docker.com/community/images/ritreshgirdhar/config https://store.docker.com/community/images/ritreshgirdhar/ms1 https://store.docker.com/community/images/ritreshgirdhar/ms2 https://store.docker.com/community/images/ritreshgirdhar/ms3 https://store.docker.com/community/images/ritreshgirdhar/gateway
#Running Demo, (pardon if the below servers are down, as i am using them for another pocs.)