Configuración centralizada con Spring Cloud Config

With dozens of microservices, scattering properties across each one becomes unmanageable. Centralized configuration stores settings in one source that every service reads from.

Spring Cloud Config provides a Config Server that serves configuration to client services, typically backed by a Git repository for versioning and auditability.

Annotate a Spring Boot app with @EnableConfigServer to turn it into a configuration hub.

Configure the server to read from a Git repo. Each service's properties live as files in that repo.

Config files are named by application and profile, such as order-service-prod.yml. The server matches requests to the right file.

• application.yml — shared defaults
• order-service.yml — per service
• order-service-prod.yml — per profile

A client service adds the config client starter and declares which application name and Config Server to use.

On startup, the client contacts the Config Server, downloads its properties, and merges them into its environment before the rest of the app initializes.

The @RefreshScope annotation lets beans pick up new values when you POST to the /actuator/refresh endpoint, avoiding full restarts.

Secrets like passwords should be encrypted. The Config Server supports encrypting values so the Git repo never stores plaintext credentials.

By using profile-specific files, the same service binary picks up dev, staging, or prod settings simply by activating the matching profile.

Centralized, versioned, refreshable config means you change a setting once, audit who changed it, and roll it out without rebuilding services.

You set up a Config Server backed by Git, connected client services, used profile-specific files, and enabled live refresh with @RefreshScope. Centralized config keeps a fleet of microservices consistent and manageable.