One of the major issues of the cloud-native application is maintaining and distributing configuration across the distributed services; developers spend lot of time configuring each environment-specific configuration. But at the time of scaling our service horizontally, we have to again reconfigure our services. Spring Cloud provides a module or sub-project for this cloud-native problem. This module is known as a Spring Cloud Config.

Spring Cloud Config is a sub-project of the Spring Cloud ecosystem. It provides a server and client approach to store and sever distributed configurations across several environments and distributed systems.

External configuration management is centralized and upheld by a Git repository. The configuration assets delineate to the Spring environment, but could be utilized by non-Spring applications if we wanted. We can create an external configuration and we can use the existing configuration on the central place, such Git version control. Spring Cloud Config provides support for both creating and using the configuration:

• Spring Cloud Config Server
• Spring Cloud Config Client

This configuration fits very well in the Spring application and you use it through Environment, PropertySource or @Value for any environment with any programming language. In the Continuous Deployment (CD) pipeline, a Spring application moves from deployment to test and then test to production; you can easily manage the configurations in all environments. It also ensures that the Spring application has every resource at every place, which is required for running at the time of its migration.

By default, the Spring Cloud Config Server uses Git implementation. It also easily supports labelled versions of configuration environments. But you can easily add alternative implementations and plug them in with Spring configuration.

Let's solve this configuration problem, and accumulate all of our configurations into a single Git repository and connect that to one application that manages a configuration for all our applications. We are going to be setting up a very simple implementation.