Migrating a real‑world application to Quarkus
summary
A step-by-step migration from a Spring application to Quarkus, measuring memory, startup and cost improvements: RSS drops from ~389 MB (Spring) to ~271 MB (Quarkus with Spring-compat) and ~266 MB (Quarkus with Panache + reactive core), with a GraalVM native image down to ~44 MB. Startup time falls from ~5 s (Spring) to ~1.6 s (Quarkus) and ~0.42 s (native), using build-time processing, Vert.x/Netty reactive core, Panache, Spring compatibility and GraalVM; local and EC2 throughput tests show higher concurrency and fewer instances, though native GC can cause occasional latency spikes.
AI-written summary · about
chapters (7)
- 0:00Start
- 8:49The Quarkus Way enables Native compilation
- 10:56Imperative Execution Model
- 13:22Reactive Core
- 14:49Quarkus smart Routing
- 16:18The famous "enterprise" microservice
- 42:50A Kafka Streaming Application
related talks
59mQuarkus for Spring Developers
31mMigrate to Quarkus, this is the way
44mMigrate Spring Boot App to Quarkus. Stage Unlocked
42mMigration to Quarkus
44mMigrate Spring Boot app to Quarkus. Stage unlocked
48mWhy Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
45mFaster, greener, and happier- why Quarkus should be your next tech stack
44mQuarkus: Supersonic Subatomic Java