Quarkus for Spring Developers
summary
Compares a Spring Boot app converted to Quarkus (no code changes) and measures real metrics: using Maven, GraalVM, Postgres and Testcontainers, Spring on the JVM averages time to first request 3.03s and RSS ~354MB; Spring native builds with GraalVM (8.3GB build RSS) give 0.39s and ~133MB. Quarkus on the JVM is 1.41s/245MB; Quarkus native builds faster (6.9GB build RSS), produces a 73MB binary and hits 0.20s and ~61MB after use. Dev mode auto-spawns containers and supports continuous testing and live reload; throughput density improves ~2–4x.
AI-written summary · about
chapters (17)
- 0:00Introduction and background
- 1:25Java history and trade-offs
- 8:26Quarkus origins and goals
- 18:34Demo setup and Spring app overview
- 21:04Spring app performance metrics
- 24:36Native image compilation
- 26:44Native image build analysis
- 27:47Native image performance metrics
- 29:21Migrating Spring to Quarkus
- 36:26Quarkus Dev mode and testing
- 37:49Code cleanup and simplification
- 41:20Test conversion to Quarkus
- 46:12Quarkus blocking vs non-blocking
- 48:16Quarkus JVM performance metrics
- 50:31Quarkus Native performance metrics
- 54:08Benchmarking results summary
- 57:21Environmental impact of Quarkus
related talks
46mMigrating a real‑world application to Quarkus
44mQuarkus: Supersonic Subatomic Java
54mEnterprise Framework Battle: Quarkus vs. Spring Boot
48mWhy Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
31mMigrate to Quarkus, this is the way
51mKubernetes Native Spring apps on Quarkus
46mQuarkus why, how and what
54mQuarkus: Java development turned into delight