Migration to Quarkus
summary
Migrates a Spring PetClinic clone to Quarkus, replacing Spring MVC, Spring Data JPA and Spring Security with JAX-RS, Panache/fine repository, Quarkus security and JDBC extensions and OpenAPI, while keeping some Spring-compat extensions when needed. Reports native GraalVM startup <0.5s, memory ~16MB, JVM Quarkus ~2.7s and ~300MB vs Spring ~8s and ~600MB, but native builds are larger and slower to compile. Notes missing reflection/AOP, gaps for Spring query-DSL and test-role injection; overall migration succeeds with trade-offs.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:47What is Quarkus
- 9:46Why migrate from Spring
- 13:39Migration steps and CDI
- 17:47REST and security migration
- 20:48Metrics and validation
- 25:55Testing differences
- 29:00Spring extensions in Quarkus
- 31:15Performance comparison
- 36:03Summary and resources
- 40:18Migration tooling and Q&A
related talks
31mMigrate to Quarkus, this is the way
44mMigrate Spring Boot App to Quarkus. Stage Unlocked
44mMigrate Spring Boot app to Quarkus. Stage unlocked
46mMigrating a real‑world application to Quarkus
25mQuarkus Hands-on Workshop for Spring Developers
59mQuarkus for Spring Developers
51mKubernetes Native Spring apps on Quarkus
54mEnterprise Framework Battle: Quarkus vs. Spring Boot