Dynamic configuration management in microservice architecture with Spring Cloud
summary
Live-coding shows a concrete setup: a Spring Cloud Config Server backed by Git serving per-application and per-profile YAML, clients use bootstrap context to fetch values, actuator /refresh works but needs per-instance calls, and automated invalidation is solved with Spring Cloud Bus over Kafka where the config server’s monitor endpoint posts refresh events to a Kafka topic so all instances reload without redeploying; demo confirms commit IDs in logs and live updates of a premium-email suffix property.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:11Dynamic config in microservices
- 7:51Live demo: microservice setup
- 11:20Spring Cloud Config Server setup
- 13:28Config Server integration
- 21:44Client apps for dynamic updates
- 27:28Manual reload with Actuator
- 30:42Scaling updates with Spring Cloud Bus
- 32:06Kafka for event updates
- 35:46Automated refresh with Kafka
- 38:11Summary: trade-offs
related talks
43mDynamic configuration management in microservice architecture with Spring Cloud
51mBrewing the Best of All Worlds
36mTools that will help you survive in the micro-service architecture
44mLive coding: Configuring your cloud-native applications with MicroProfile Config
54mSpring Cloud: API gateway upgrade & configuration in the cloud
49mPanta rhei: runtime configuration updates with Spring Boot
01h 20mGetting Started with Spring Cloud
49mSpring Cloud *: Exploring Spring Cloud Implementations