Maintaining configurations for different microservices separately would make it difficult for the operations team. The solution, as shown in the following figure, is to create a centralized Configuration Server:

The centralized Configuration Server holds all the configuration belonging to all the different microservices. This helps in keeping the configuration separate from the application deployable.

The same deployable (EAR or WAR) can be used in different environments. However, all configuration (things that vary between different environments) will be stored in the centralized configuration server.

An important decision that needs to be made would be to decide whether there are separate instances of centralized configuration servers for different environments. Typically, you would want access to your production configuration to be more restrictive compared to other environments. At a minimum, we recommend a separate centralized configuration server for production. Other environments can share one instance of the configuration server.