The Missing Manual
⌘K
All topics / Quarkus From Zero

Quarkus From Zero

Learn the cloud-native Java framework built for fast startup and low memory: why Quarkus moves work to build time, its loved dev mode, REST APIs, build-time CDI, Hibernate with Panache, configuration, reactive programming with Mutiny, testing, and compiling to a native executable. The standards you know, made supersonic.

  1. What Quarkus Is & Why It's Fast Quarkus is a cloud-native Java framework that moves framework wiring from startup to build time, so apps boot in milliseconds, use little memory, and can compile to native machine code.
  2. Dev Mode & the Developer Experience Quarkus's signature: live reload that recompiles on the next request, a built-in Dev UI, continuous testing, and Dev Services that auto-start throwaway databases — the fast feedback loop teams fall in love with.
  3. Building REST APIs Expose a Product over HTTP with Quarkus REST (RESTEasy Reactive): the standard JAX-RS annotations, path and query params, JSON request bodies via the rest-jackson extension, RestResponse for status codes, and the imperative-vs-reactive choice.
  4. CDI in Quarkus (ArC) Quarkus's DI container is ArC: the same CDI standard — @Inject, @ApplicationScoped — but the wiring graph is computed at build time, which is what makes fast boot and native images possible.
  5. Persistence: Hibernate with Panache Panache is a thin Quarkus layer over Hibernate ORM that strips the boilerplate. Learn active-record and repository patterns, simplified queries, transactions, and zero-config Dev Services databases.
  6. Configuration How Quarkus externalizes config with MicroProfile: application.properties, @ConfigProperty, type-safe @ConfigMapping, dev/test/prod profiles, source precedence, and the build-time vs runtime trap unique to Quarkus.
  7. Reactive Quarkus with Mutiny Demystifies reactive Quarkus: why non-blocking exists, Mutiny's Uni and Multi, building reactive pipelines and endpoints with reactive Panache, and the honest verdict on when reactive earns its complexity versus plain imperative.
  8. Testing Quarkus Apps @QuarkusTest boots a real app fast enough to lean on, REST Assured asserts the HTTP contract, Dev Services hands tests a real database, and @QuarkusIntegrationTest runs the suite against the native binary.
  9. Native Compilation & Containers How Quarkus compiles your Product service to a standalone native executable with GraalVM, why build-time wiring makes that possible, the reflection gotcha, and packaging tiny containers for Kubernetes.
  10. Production & Where to Go Next You can build a fast Quarkus service and know why it's fast. Here's the production essentials — health, metrics, tracing, Kubernetes — the extension ecosystem, an honest look at the field, and what to build next.