Java / Quarkus Interview questions
What is the difference between Quarkus and Spring Boot?
Both are popular frameworks for building Java microservices, but they differ fundamentally in when the bulk of application wiring happens and what that means for startup performance and native-image compatibility.
| Quarkus | Spring Boot |
| Most wiring (DI graph, annotation scanning) resolved at build time. | Wiring largely happens at runtime via classpath scanning and reflection. |
| Native-image compilation is a first-class, well-supported path. | Native support exists (Spring Native/AOT) but historically less mature. |
| Startup typically faster, especially in native mode. | Startup slower in JVM mode due to runtime reflection-heavy bootstrap. |
| Smaller, curated extension ecosystem. | Much larger, longer-established library and community ecosystem. |
Neither is strictly "better" in the abstract: teams already deeply invested in the Spring ecosystem often stay there for its maturity and library breadth, while teams prioritizing container density, cold-start time, or greenfield cloud-native services frequently find Quarkus's build-time model a better fit out of the box.
When does most of Quarkus's dependency wiring happen?
What is a commonly cited strength of the Spring Boot ecosystem?
More Related questions...
