Migrate to Quarkus, this is the way
summary
Migrates a Spring Boot PetClinic REST app to Quarkus using Hibernate Panache, JAX‑RS, Quarkus security, OpenAPI, caching and metrics; verifies build-time Spring compatibility via Spring Quarkus extensions and suggests testcontainers for integration tests. Observes startup dropping from ~7s (Spring Boot) to 2.5s (Quarkus JVM) to <0.5s native and memory from ~700MB to 200MB to ~21MB when compiling with GraalVM native image. Notes missing AOP support, no expression‑language for role checks, and testing role injection is harder.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:31What Is Quarkus
- 5:34The Facts of Quarkus
- 7:25About the Quarkus Evolution
- 8:03Memory
- 9:02Response Time
- 11:19Why I Decided To Try this Migration
- 14:45Migration Steps
- 17:21Security
- 18:48Metrics
- 22:44Test Resources
- 28:20Coding
- 28:46Migration Toolkit for Applications
- 30:09Use Cases
related talks
44mMigrate Spring Boot App to Quarkus. Stage Unlocked
42mMigration to Quarkus
44mMigrate Spring Boot app to Quarkus. Stage unlocked
46mMigrating a real‑world application to Quarkus
59mQuarkus for Spring Developers
25mQuarkus Hands-on Workshop for Spring Developers
54mEnterprise Framework Battle: Quarkus vs. Spring Boot
49mQuarkus Intro