Reactifying your application
summary
Reactive replaces blocking DB fetches with streaming results so users see the first item immediately, claims reduced resource usage and better responsiveness, and reports successful POCs using Project Reactor with Spring 5 and experiments with Vert.x and Akka; warns that most SQL drivers are still experimental while Cassandra/MongoDB have better support. Recommends designing for failure (Netflix patterns, supervision), testing with StepVerifier, avoiding aggregates that force blocking, and using composable method references for debuggability.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:21What can you expect
- 4:31Frameworks
- 6:57Dont overreact
- 7:54Change your mindset
- 9:21Design for failure
- 11:16Dont block
- 11:44Testing
- 12:27Debugging
- 13:17Composable method references
- 13:43Recap
related talks
40mReactive programming: lessons learned
46mGet Reactive! Programming, Systems, and Microservices
42mReacting to the Future of Application Architecture
40mREACTIVE A New Hope! Learn From a Performance History
34mReactive Architecture
45mReactive web services
55mRethinking Reactive Architectures
54mReactive for CRUD: fantasies and reality