Full Stack Development with JHipster

Spring cloud config server

In a microservice architecture, the services are dynamic in nature. They will go down and come up based on traffic or any other configuration. Due to this dynamic nature, there should be a separate, highly available server that holds the essential configuration details that all the servers need to know.

For example, our pricing service will need to know where the registry service is and how it has to communicate to the registry service. The registry service, on the other hand, should be highly available. If for any reason the server has to go down, we will spin up a new server. The pricing service needs to communicate with the config service in order to find out about the registry service. On the other hand, when ...