Backend Technologies · Java
Quarkus — Free Learning Resources
Free, printable resources for Quarkus — practice problems, quick-reference cheatsheet, and an interview prep sheet. No sign-up required.
Quarkus — Practice Worksheet
Structured exercises and problems to build hands-on Quarkus skills. Work through key concepts step by step.
Quarkus — Cheatsheet
One-page quick-reference for Quarkus — key syntax, commands, patterns, and best practices at a glance.
Quarkus — Interview Sheet
Top Quarkus interview questions with concise answers. Get ready for any technical round with this focused prep sheet.
About Quarkus
Quarkus is a Kubernetes-native Java framework optimized for GraalVM native image compilation and low-resource cloud deployments. It achieves sub-second startup times and a fraction of the memory footprint of Spring Boot, making it ideal for serverless functions, containers, and microservices.
QuarkusCheat Sheet — What's Covered
- ✓Build modes — JVM mode vs. native image compilation with GraalVM
- ✓CDI dependency injection and @ApplicationScoped, @RequestScoped
- ✓RESTEasy Reactive and Mutiny — reactive REST endpoints
- ✓Panache ORM — simplified Hibernate with Active Record pattern
- ✓Dev Mode — live reload, Dev UI, and Dev Services for zero-config local development
Frequently Asked Questions — Quarkus
What makes Quarkus faster to start than Spring Boot?
Quarkus moves most framework work to build time — dependency injection wiring, configuration resolution, and classpath scanning happen during the build, not at startup. This reduces runtime work to near zero, enabling millisecond startup vs. seconds for traditional JVM apps.
What is GraalVM native image compilation in Quarkus?
Native compilation converts the JVM app into a native binary with no JVM required. Run mvn package -Pnative to produce a native executable. It starts in under 100ms and uses 50-90% less memory, at the cost of longer build times and some JVM reflection limitations.
What is Panache in Quarkus?
Panache simplifies Hibernate usage with two patterns: Active Record (entity methods directly on the model class: Person.findById(id)) and Repository (separate repository class). Both reduce boilerplate compared to standard JPA repositories.
What is Quarkus Dev Mode?
Run quarkus dev to start live reload — source changes are picked up without restart. Dev UI at localhost:8080/q/dev provides extension dashboards. Dev Services automatically starts Docker containers for databases, Kafka, etc. — zero configuration for local development.
When should you choose Quarkus over Spring Boot?
Choose Quarkus when startup time and memory footprint matter — containerized microservices, serverless functions, or tight resource environments. Choose Spring Boot for rich ecosystem, team familiarity, or when native compilation constraints (reflection, proxies) are a concern.
Who Is This For?
Java developers building cloud-native microservices or serverless functions who need faster startup times and lower memory usage than traditional JVM frameworks.