Migrating from Imperative to Reactive
summary
Shows how to migrate a Spring Boot webmvc app to WebFlux by switching annotations to the functional route+handler API, replacing spring-webmvc with spring-webflux and JPA/JDBC with R2DBC reactive repositories; introduces Mono (0..1) and Flux (unbounded), reintroduces a distributed cache (Hazelcast or similar) to avoid DB hits, and uses BlockHound at runtime to detect blocking calls. Demonstrates that schema and connection setup must be written manually, and argues reactive reduces resource use and improves perceived performance under load.
AI-written summary · about
chapters (6)
- 0:00Introduction to reactive migration
- 10:10Migrating from annotations to functional API
- 25:15Switching to WebFlux and Project Reactor
- 35:43Reactive database with R2DBC
- 50:06Blocking calls and BlockHound tool
- 58:18Resources and Q&A
