Enterprise Framework Battle: Quarkus vs. Spring Boot
summary
Compares two concrete implementations of a planets REST app using Maven, Postgres, Hibernate/JPA (Panache in Quarkus), OpenAPI, health checks, metrics and integration tests (JUnit5 + RestAssured). Quarkus compiles injection metadata at build time, produces a tiny runner and time to first response ~0.5s vs ~6–7s for Spring Boot; Spring wins for its repository magic and wider ecosystem. Quarkus hot reload is request-triggered and supports continuous selective testing with dev services (DB containers); overall claim: smaller executable, lower runtime memory.
AI-written summary · about
chapters (25)
- 0:00Introduction and overview
- 1:31Purpose of the comparison
- 3:01Demo application overview
- 5:13Spring Boot project setup
- 6:16Spring Boot entity and repository
- 9:27Spring Boot REST API and injection
- 12:02Spring Boot service and configuration
- 13:29Spring Boot DevTools and live reload
- 16:09Spring Boot configurable values
- 17:15Spring Boot health checking
- 20:07Quarkus project setup
- 21:55Quarkus entity and Panache
- 23:44Quarkus REST API and injection
- 25:05Quarkus database access methods
- 26:51Quarkus injection and CDI
- 27:59Quarkus configurable values
- 29:26Quarkus build and startup
- 32:18Quarkus application demo
- 33:24Quarkus DevMode and hot reload
- 37:02Quarkus health checking
- 39:39Testing in Quarkus and Spring Boot
- 43:36Continuous testing in DevMode
- 45:43Performance and production metrics
- 47:10Summary and GitHub project
- 47:35Q&A session
related talks
59mQuarkus for Spring Developers
31mMigrate to Quarkus, this is the way
01h 06m2020 - A space odyssey with Micronaut and Quarkus
40mWhy Quarkus.io Is Cooler Than Spring
44mQuarkus: Supersonic Subatomic Java
49mQuarkus Intro
48mWhy Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
51mKubernetes Native Spring apps on Quarkus