Embracing Virtual Threads
summary
Helidon 4.4 (Apr 2026) abandons its Netty-based async core and rewrote web server to a virtual-thread model, allocating one virtual thread per request so handlers can block safely; results are higher throughput, predictable latency and “no drama” scaling. 4.4 adds LangChain for J integration with blocking Java streams and Agentic support, targets Java 26, uses compile-time annotations that generate source, and expresses intent to move Helidon to OpenJDK.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:58Helidon's Ethos & Structure
- 2:16Embracing Virtual Threads
- 7:29Helidon Support for AI
- 9:35Becoming OpenJDK
- 12:50Helidon 4.4
related talks
45mVirtual Threads in the Real World: Fast, Robust Java Microservices with Helidon
49mRevolutionizing Microservices Development with Helidon 4!
01h 13mReactive vs. Virtual threads power with Helidon Nima
43mWhat's Coming in Helidon 4
41mHelidon - Microservices on Modern Java
44mVirtual Threads in Action!
47mVirtual Threads power with Helidon Nima
31mFly like a rocket with Helidon
