Going Reactive with Helidon!
summary
Helidon SE exposes a pure Java reactive engine built on java.util.concurrent.Flow with Multi and Single types, a nonblocking reactive web server, a reactive WebClient and an async DB wrapper that runs blocking drivers on dedicated executors. Reactive messaging connects Kafka, AQ and websockets as channels with back pressure. Demo shows a 10 MB native executable and reactive flow handling ~27,000 requests while a blocking MP server starves quick requests. Enabling virtual threads via one JVM flag brings blocking code close to reactive performance.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:06What is Helidon?
- 7:05Reactive programming explained
- 13:25Helidon Reactive engine
- 16:16Quick start demo
- 20:29Reactive messaging with Kafka
- 25:46Reactive database access
- 31:43Project Loom and virtual threads
- 35:39Live demo: Loom vs reactive
- 44:50Nemo: Future of Helidon servers
- 47:19Closing and Q&A
