Reactive or Not Reactive, That Is the Question
summary
The talk examines applying reactive programming to an existing Java system: it shows a problematic codebase, attempts a reactive-style refactor (likely using reactive Java APIs), and analyzes the pros and cons of the reactive approach and specific reactive APIs. It compares system complexity before and after the refactor, highlighting which benefits are real and which are just trendy or harmful.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:06Problem statement and example system
- 3:32Buffer issues and service failures
- 9:56Solution with adaptive balancer
- 23:15Project Reactor and Spring WebFlux intro
- 27:56WebFlux setup and client config
- 30:51Controller changes and stream handling
- 35:45Missing request body error
- 41:00Terminal operations and controller return
- 43:52Direct Buffer Memory issue
- 50:39Direct Buffer Memory cause
- 54:31WebSocket intro and solution comparison
- 1:01:56Summary and technology comparison
related talks
41mThe definite guide to reactive programming in Java
52mReactive for the Impatient - A Gentle Intro to Reactive Java
01h 03mReactive Enterprise Java
01h 42mReactive Programming: creating highly responsive applications
24mBringing Reactive Programming to Java and Microservices
27mReactive: Understand and Embrace
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
47mReactive Programming - Royal Road or Wrong Turn?
