A Configuration Server allows us to serve any microservice the configuration that it may need, so when a microservice starts, it will require no more configurations than just the one from where the Configuration Service is located.
In order to serve that configuration, we can use a variety of backends, from our machine filesystem or a Git repository that will include our configuration files, to a database.
A single config server can be used to provide configuration for several applications, and at the same time, we can provide a set of configurations that we can share with them.
Finally, a Configuration Server can manage application profiles. This gives us the ability to get different configurations based on how we start our microservice. This flexibility can be employed for a range of uses, from varying the configuration per environment to different configuration...