In this article, we explore the concept of centralized configuration, in the context of microservices.
You will learn
- What is a Cloud config server?
- What is centralized configuration?
- Why do we need centralized configuration in microservices architectures?
- What are the important features of Spring Cloud Config Server?
Why Centralized Configuration?
When we talk about microservices architecture, we visualize a large number of small microservices talking to each other. The number of microservices depends on the size of the enterprise.
The interesting part is that each of these microservices can have its own configuration.
Such configuration includes details such as:
- Application configuration
- Database configuration
- Communication Channel Configuration - queues and other infrastructure
- URLs of other microservices to talk to
In addition, each microservice would have a separate configuration for different environments, such as development, qa and production.
If maintaining a single configuration for a large application is difficult, imagine maintaining configurations for hundreds of microservice in different environments
Centralized Config Server To The Rescue
That’s where a centralized configuration server steps in.
Configuration for all microservices (for all environments) is stored at one place - a centralized configuration store.
When a microservice needs its configuration, it provides an id at launch - a combination of microservice name and the environment.
The centralize config server looks up the configuration and provides the configuration to the microservice.
Ensure that the configuration in centralized config server is secured and has role based access.
Introducing Spring Cloud Config Server
Spring Cloud Config Server is one of the popular implementations of a cloud config server.
Spring Cloud Config Server enables you to store all the configuration for multiple microservices for different environments in a Git or a SVN Repository. A set of folder structures and conventions need to be followed for the setup to work.
A microservice can connect to the config server and identify itself, and also specify the instance it represents. This enables it to get the required configuration.
The setup ensures that the operations team does not need to take time out to configure the individual microservices on a case-by-case basis. All that they need to worry about is to configure the centralized config server, and start putting relevant configuration into the Git repository.
Automatically picking up configuration changes
An interesting feature present with the Spring Cloud Config Server, is auto refresh.
Whenever a change is committed to the Git repository, configuration in the application is auto-refreshed.
In this article, we looked at why we need centralized configuration in microservices based applications. We looked at how the Spring Cloud Config Server manages centralized configuration.
Cloud and Microservices Terminology
This is the article in a series of six articles on terminology used with cloud and microservices:
- 1 - Microservices Architectures - What is Service Discovery?
- 2 - Microservices Architectures - Centralized Configuration and Config Server
- 3 - Microservices Architectures - API Gateways
- 4 - Microservices Architectures - Importance of Centralized Logging
- 5 - Microservices Architectures - Introduction to Auto Scaling
- 6 - Microservices Architectures - What is Fault Tolerance?