Panta rhei: runtime configuration updates with Spring Boot
summary
Spring Boot applications pick up live config using Spring Cloud Context: enabling the refresh actuator endpoint and posting or using a backend (demo uses Spring Cloud Console/Consul) rebonds @ConfigurationProperties, updates log levels and triggers @RefreshScope proxies replace targets so refresh-scoped beans are recreated (predestroy/postconstruct run; counters reset). Kubernetes uses a separate Configuration Watcher that delays notifications (demo sets Config Watcher waits 30s), binding/validation can fail and shows a refresh-scope health indicator down, and Hikari pool reloads require caution.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 3:56Restarting apps for config changes
- 12:07Spring Cloud Context basics
- 20:09Automatic refresh with external sources
- 31:06Binding errors and validation
- 32:57Kubernetes config reload
- 43:44Key considerations
- 47:15Summary
related talks
40mDynamic configuration management in microservice architecture with Spring Cloud
51mHitting the “refresh” button on your Spring web application
44mWhat's New in Spring Boot 2.0
43mInside Spring: The Architecture Behind the Framework
13mReactive-Config will Hocon you... so Don't Stop The Appli \o/
40mGood for Karma: Configuration at Runtime
01h 34mBoot yourself, Spring is coming
08mThe nervous system of Spring Framework