Dynamic configuration updates in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is dynamic configuration update in microservices?

It is the ability to change service settings or parameters at runtime without restarting the service, allowing quick adaptation to new conditions.

beginner

Name a common tool used for managing dynamic configuration in microservices.

Tools like Consul, etcd, or Spring Cloud Config Server are commonly used to store and distribute configuration dynamically.

intermediate

Why is it important to avoid service restarts when updating configuration?

Avoiding restarts prevents downtime and service disruption, ensuring continuous availability and better user experience.

intermediate

What is a common pattern to notify microservices about configuration changes?

Using a publish-subscribe pattern where configuration changes are published and services subscribe to receive updates in real-time.

advanced

How can microservices ensure consistency when configuration updates happen concurrently?

By using versioning, atomic updates, and distributed locks to coordinate changes and avoid conflicts.

Which of the following best describes dynamic configuration updates?

A Changing service settings without restarting the service

B Restarting services to apply new settings

C Hardcoding configuration in the service code

D Ignoring configuration changes during runtime

Dynamic configuration updates allow changing settings without restarting, enabling seamless updates.

Which tool is NOT typically used for dynamic configuration management?

A Consul

B etcd

C GitHub Actions

D Spring Cloud Config

GitHub Actions is for CI/CD workflows, not configuration management.

What pattern helps microservices get notified about config changes?

A Polling only

B Publish-subscribe

C Batch processing

D Request-response

Publish-subscribe allows real-time notifications of config changes.

Why is versioning important in dynamic configuration updates?

A To track and manage different config states safely

B To slow down updates

C To delete old configurations immediately

D To avoid using configuration files

Versioning helps track changes and avoid conflicts during updates.

What is a risk if configuration updates require service restarts?

A Automatic scaling

B Faster updates

C Improved performance

D Service downtime and user disruption

Restarting services causes downtime, affecting availability.

Explain how dynamic configuration updates improve microservice availability and flexibility.

Think about how services stay running while configs change.

Describe common methods and tools used to implement dynamic configuration updates in microservices.

Consider how services get and apply new settings safely.

Practice

1. What is the main benefit of using dynamic configuration updates in microservices?

easy

A. Encrypt all service communication by default

B. Change service settings without restarting or downtime

C. Reduce the size of service containers

D. Increase the number of microservices automatically

Solution

1. Step 1: Understand dynamic configuration updates

   Dynamic configuration updates allow changing settings while the service is running.

2. Step 2: Identify the main benefit

   This avoids restarting services, preventing downtime and improving flexibility.

3. Final Answer:

   Change service settings without restarting or downtime -> Option B

4. Quick Check:

   Dynamic config = no downtime updates [OK]

Hint: Dynamic config means no restart needed for changes [OK]

Common Mistakes:

• Confusing dynamic config with scaling services
• Thinking it reduces container size
• Assuming it encrypts communication automatically

2. Which of the following is a common method for microservices to receive dynamic configuration updates?

easy

A. Polling a central configuration server periodically

B. Hardcoding config values in source code

C. Restarting the service every hour

D. Using static environment variables only

Solution

1. Step 1: Review methods for dynamic config updates

   Common methods include polling or push from a central config server.

2. Step 2: Identify the correct method

   Polling a config server lets services fetch updates regularly without restart.

3. Final Answer:

   Polling a central configuration server periodically -> Option A

4. Quick Check:

   Polling config server = dynamic updates [OK]

Hint: Dynamic config needs active update fetching, not static values [OK]

Common Mistakes:

• Thinking hardcoded values can update dynamically
• Assuming restart is needed for updates
• Believing static env vars update automatically

3. Consider this pseudocode for a microservice fetching config updates:

config = load_config()
while True:
    if config_server.has_update():
        config = config_server.get_update()
    sleep(10)
    print(config['feature_flag'])

What will this code do when the feature_flag changes on the config server?

medium

A. Print the old feature_flag value forever

B. Crash because config_server.has_update() is undefined

C. Print nothing because of missing initial config

D. Update and print the new feature_flag value every 10 seconds

Solution

1. Step 1: Analyze the update check loop

   The code checks if the config server has an update, then fetches it.

2. Step 2: Understand the print behavior

   Every 10 seconds it prints the current feature_flag from the updated config.

3. Final Answer:

   Update and print the new feature_flag value every 10 seconds -> Option D

4. Quick Check:

   Polling loop updates config = prints new value [OK]

Hint: Polling loop updates config then prints latest value [OK]

Common Mistakes:

• Assuming config never updates after initial load
• Thinking code crashes due to undefined methods (assumed defined)
• Ignoring the sleep and print inside the loop

4. A microservice uses a push-based config update system but sometimes misses updates. What is a likely cause?

medium

A. The service does not acknowledge receipt of updates

B. The service polls the config server too frequently

C. The service restarts after every update

D. The config server uses static environment variables

Solution

1. Step 1: Understand push-based config update mechanism

   Push systems send updates and expect acknowledgments to confirm delivery.

2. Step 2: Identify why updates are missed

   If the service does not acknowledge, the server may not resend or confirm updates.

3. Final Answer:

   The service does not acknowledge receipt of updates -> Option A

4. Quick Check:

   Missing ack = missed updates in push system [OK]

Hint: Push updates need acknowledgments to avoid missing data [OK]

Common Mistakes:

• Confusing push with polling frequency issues
• Assuming restarts cause missed updates
• Thinking static env vars relate to push update failures

5. You design a microservices system with dynamic config updates using a central config server. To ensure minimal latency and high availability, which approach is best?

hard

A. Embed config in each service and restart services on config change

B. Use a single config server with clients polling every second

C. Deploy multiple config server replicas with push notifications and local caching

D. Use static config files updated manually on each service host

Solution

1. Step 1: Consider latency and availability needs

   Multiple replicas reduce single points of failure and improve response times.

2. Step 2: Evaluate update delivery methods

   Push notifications with local caching reduce latency and avoid constant polling.

3. Final Answer:

   Deploy multiple config server replicas with push notifications and local caching -> Option C

4. Quick Check:

   Replicas + push + cache = low latency & high availability [OK]

Hint: Replicas + push + cache = best for latency and availability [OK]

Common Mistakes:

• Relying on single server causes downtime
• Polling every second wastes resources
• Restarting services causes downtime
• Manual static updates are error-prone and slow