Less waste, more joy, and a lot more green: How Quarkus makes Java better
summary
Quarkus compiles to native via GraalVM and yields 15 milliseconds start time and roughly half the memory footprint of typical Java apps, while Quarkus-on-JVM delivers surprisingly higher throughput than competitors. The engineering team finds and fixes low‑level issues (cache pollution found by reading assembly) that tripled throughput on microbenchmarks and delivered a 30% hotspot win with a non‑idiomatic code change. Tooling includes Janex offline indexes, Testcontainers for dev services, live coding and continuous testing; build‑time bootstrapping moves work out of startup and it works.
AI-written summary · about
chapters (18)
- 0:00Quarkus goals
- 1:06Quarkus and performance
- 3:12Startup vs throughput trade-offs
- 6:02Developer joy in Quarkus
- 7:52Eliminating waste for speed
- 10:19Debugging with TechEmpower
- 14:38Cache pollution fixes
- 18:33Challenging performance assumptions
- 21:19Runtime to build time
- 25:18Extending Quarkus efficiency
- 26:46Live coding feedback
- 28:12Tight feedback loops
- 30:41Reducing boilerplate
- 33:28Magic vs debuggability
- 34:36Why developer joy matters
- 36:03Lowering cloud costs
- 37:46Vroom model energy efficiency
- 40:58Summary Quarkus benefits
related talks
52mQuarkus Supersonic Subatomic Java
45mQuarkus Unleashed
42mWill my library or framework work on Quarkus (and GraalVM)?
51mQuarkus and GraalVM: booting Hibernate at supersonic speed, subatomic size
49mCloud Native Java for This Decade With Quarkus
46mWriting Greener Java Applications
49mJava Particle Acceleration using Quarkus
49mComparing Java startup performance options with Quarkus