Reactive Programming - Royal Road or Wrong Turn?
summary
The talk examines reactive programming in Java frameworks like Quarkus and Helidon as a way to reduce thread usage by avoiding blocking calls, but argues this yields hard-to-read code and new operational challenges. It evaluates code and runtime benefits of reactive approaches and compares them to a simpler alternative using virtual threads from Project Loom with more straightforward, blocking-style code.
AI-written summary · about
chapters (7)
- 0:00Reactive programming intro
- 10:16Synchronous parallelization with Futures
- 15:12Blocking Futures problems
- 22:16Project Loom and virtual threads
- 31:07Virtual threads benefits
- 36:25Framework support
- 41:08Summary and conclusion
related talks
01h 56mConcurrency Crossroads: Choosing between Reactive Programming & Virtual Threads
01h 06mReactive or Not Reactive, That Is the Question
41mThe definite guide to reactive programming in Java
47mFrom Imperative to Reactive Programming
28mReactive Quarkus
24mBringing Reactive Programming to Java and Microservices
02h 51mReactive Microservices with Quarkus
01h 42mReactive Programming: creating highly responsive applications