Reactive vs. Virtual threads power with Helidon Nima
summary
Helidon demonstrates that replacing reactive plumbing with JDK virtual threads delivers similar or better throughput while keeping blocking, familiar code. Demo shows three modes: Netty with classic threads (slow under blocking IO), reactive Helidon SE (high CPU utilization, few errors), and virtual-thread mode or change one property to enable virtual threads which matches reactive performance. Helidon adds Nima: virtual-thread native web server built on JDK features (HTTP/1, HTTP/2, gRPC, WebSocket, TLS), wraps blocking JDBC for reactive APIs, and claims Oracle Hospitality handles millions of requests per second with 10MB services.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 7:25Spring Boot
- 15:04Reactive vs Nonblocking
- 17:11Helidon NP
- 18:10Distributing your product
- 19:58Native Image
- 25:26Reactive Player
- 29:12Reactive Engine
- 32:12Reactive Web Server
- 37:53Reactive Messaging
- 38:44Reactive Programming
- 44:21Virtual Threads
- 52:05Demo
- 54:43Demo with server
related talks
47mVirtual Threads power with Helidon Nima
45mVirtual Threads in the Real World: Fast, Robust Java Microservices with Helidon
14mEmbracing Virtual Threads
44mVirtual Threads in Action!
49mRevolutionizing Microservices Development with Helidon 4!
41mHelidon - Microservices on Modern Java
43mWhat's Coming in Helidon 4
52mGoing Reactive with Helidon!