Config server pattern in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Config Server Pattern in microservices?

It is a design pattern where a central server stores configuration settings for multiple microservices, allowing them to fetch their configs dynamically at runtime.

beginner

Why use a Config Server instead of local config files?

A Config Server centralizes configuration, making it easier to update settings for many services without redeploying them individually.

intermediate

How does a microservice typically get its configuration from a Config Server?

The microservice calls the Config Server API during startup or refresh to retrieve its configuration data, often using service name and profile as keys.

intermediate

What is a common storage backend for Config Servers?

Config Servers often use Git repositories or centralized databases to store configuration files securely and version-controlled.

advanced

Name one challenge when using Config Server Pattern and how to address it.

Challenge: Config Server downtime can affect microservices startup. Solution: Use caching and fallback configs locally to handle temporary unavailability.

What is the main role of a Config Server in microservices?

A Store and serve configuration centrally

B Manage service discovery

C Handle user authentication

D Balance network traffic

The Config Server stores configuration centrally and serves it to microservices.

Which storage is commonly used by Config Servers to keep config files?

A Git repository

B Local service disk only

C User browser cache

D Load balancer

Git repositories are commonly used for version-controlled config storage.

How do microservices usually fetch their configuration from a Config Server?

A By sending email requests

B By polling a database every second

C By reading local environment variables only

D By calling Config Server API at startup

Microservices call the Config Server API during startup or refresh to get configs.

What is a key benefit of using a Config Server Pattern?

A Faster database queries

B Centralized config management

C Improved UI design

D Automatic code compilation

Centralized config management simplifies updates and consistency.

What should microservices do if the Config Server is temporarily unavailable?

A Crash immediately

B Wait indefinitely

C Use cached or fallback configs

D Restart the Config Server

Using cached or fallback configs helps maintain service availability.

Explain the Config Server Pattern and its benefits in microservices architecture.

Think about how multiple services get their settings from one place.

Describe a typical request flow when a microservice fetches configuration from a Config Server.

Imagine how a service asks for its settings when it starts.