Quarkus 3: Elevating Java Microservices with Project Loom and Beyond
summary
Quarkus 3 runs Java 21 virtual threads so imperative endpoints scale without rewriting to reactive code, enabled by a single annotation that switches routes onto Java 21 virtual threads. Demo uses Quarkus DevServices and Testcontainers with JPA backed by Hibernate ORM 6, and shows ~3,734 transactions/second on a laptop. Caveats: synchronized, thread‑local or blocking libs pin virtual threads, container limits reduce gains, and throughput drops past very high concurrency (e.g. ~22k).
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 2:03Java threading evolution
- 8:34Reactive programming
- 14:52Introduction to virtual threads
- 22:48Quarkus demo and features
- 29:43Quarkus vs. Spring Boot
- 40:13Challenges with virtual threads
- 47:23Conclusion and resources
related talks
51mQuarkus 3: The Road to Loom for Cheaper, Faster, and Easier Concurrent Applications
50mQuarkus 3: The Road to Loom for Cheaper, Faster, and Easier Concurrent Applications
41mServices Reloaded Increased Throughput with Project Loom Virtual Threads
49mQuarkus, the Java Stack back from the Future
51mQuarkus why, how and what
01h 56mConcurrency Crossroads: Choosing between Reactive Programming & Virtual Threads
34mLets be Real Quarkus in the Wild
48mSupersonic, Subatomic Java with Quarkus