Dynamic configuration management in microservice architecture with Spring Cloud
summary
Sets up a Git-backed Spring Cloud Config server and clients using bootstrap context, Eureka discovery, and actuator endpoints; demonstrates manual reload via POST /actuator/refresh and automated propagation using Spring Cloud Bus over Kafka and the config server’s /monitor endpoint. Example runs with three services (gateway, customer-manager, product-manager) each as one instance, changes pushed to Git update properties (premium email suffix) and are applied live without rebuilds or restarts.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:43About Bartomiej
- 2:10Agenda
- 3:07Why should we care about configuration
- 6:30Example overview
- 7:37Eureka dashboard
- 8:17Demo
- 12:28Complex server
- 14:42Spring Initializer
- 26:18Demonstration
- 31:38Solution
- 33:28Implementation
- 37:43Experiment
related talks
40mDynamic 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
53mBooting your micro-services architecture with Spring and Netflix
54mSpring Cloud: API gateway upgrade & configuration in the cloud
53mThe Beginner’s Guide To Spring Cloud
49mSpring Cloud *: Exploring Spring Cloud Implementations
52mBuilding a typical Spring Cloud architecture application
