Quarkus from inside
summary
Quarkus compiles Java apps ahead-of-time into tiny, fast natives: an 8 ms demo runs from a 19 MB native executable that uses ~18 MB RSS. It does this via build-time boot and Quarkus extensions that record wiring and eliminate runtime scanning, then hands outputs to GraalVM native-image under the closed world assumption. JVM mode keeps JIT, debugging and dynamic loading; native mode disables dynamic class loading, reflection unless registered, and JVM tooling but yields much higher container density.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:12Demo
- 16:51Compilation Error
- 24:05Boot Time
- 24:35Time to First Request
- 39:32Closed World Assumption
- 50:37Container Density
- 51:54Produce the Native Image
- 53:16Conclusion
- 55:39Questions
related talks
45mQuarkus Unleashed
11mAll about Quarkus
54mQuarkus: Java development turned into delight
42mKeynote: Subatomic Java Microservices with Quarkus
42mWill my library or framework work on Quarkus (and GraalVM)?
44mQuarkus: Supersonic Subatomic Java
51mQuarkus and GraalVM: booting Hibernate at supersonic speed, subatomic size
48mSupersonic, Subatomic Java with Quarkus