What is this?
Quarkus is an open-source Java framework for writing cloud-native applications, built from the start with Linux containers in mind.
Quarkus is an open-source Java framework for writing cloud-native applications, built from the start with Linux containers in mind.What does the 'Supersonic Subatomic' pitch actually buy me?Speed and size: Quarkus shifts work to build time, so apps start fast and keep a minimal footprint — exactly what you want when deploying into containers.
Speed and size: Quarkus shifts work to build time, so apps start fast and keep a minimal footprint — exactly what you want when deploying into containers.How do I go from zero to a running Quarkus app?Start with the Getting Started guide linked at the top of the README; the project wiki carries the fuller documentation.
Start with the Getting Started guide linked at the top of the README; the project wiki carries the fuller documentation.Do I have to ditch the Java libraries I already use?No — Quarkus is built on the standards you likely already have: RESTEasy and JAX-RS, Hibernate ORM and JPA, Netty, Eclipse Vert.x, Eclipse MicroProfile, and Apache Camel.
No — Quarkus is built on the standards you likely already have: RESTEasy and JAX-RS, Hibernate ORM and JPA, Netty, Eclipse Vert.x, Eclipse MicroProfile, and Apache Camel.How painful is upgrading between Quarkus versions?Upgrade notes are centralized: the project collects all migration notes in its migration guides, one place to check per release.
Upgrade notes are centralized: the project collects all migration notes in its migration guides, one place to check per release.Is it only for tiny microservices?No — it is deliberately versatile: the same framework spans everything from the smallest microservice to the largest monolith.
No — it is deliberately versatile: the same framework spans everything from the smallest microservice to the largest monolith.Do I need Kubernetes to run a Quarkus app?Kubernetes is the environment its design targets — Quarkus embraces 12-factor architecture — but nothing pins you there: being Java, apps run wherever a JVM or native binary runs.
Kubernetes is the environment its design targets — Quarkus embraces 12-factor architecture — but nothing pins you there: being Java, apps run wherever a JVM or native binary runs.Do I have to write everything in reactive style?No. Quarkus unifies imperative and reactive under one programming model, so non-blocking and imperative code can live side by side in the same application.
No. Quarkus unifies imperative and reactive under one programming model, so non-blocking and imperative code can live side by side in the same application.Can I compile my app to a native binary?Yes — two runtime modes are supported: run on the JVM for high throughput, or compile ahead-of-time to a native executable for constrained environments.
Yes — two runtime modes are supported: run on the JVM for high throughput, or compile ahead-of-time to a native executable for constrained environments.When does the next release come out?Quarkus keeps a public release planning document (linked in the README) where upcoming releases and their timing are tracked.
Quarkus keeps a public release planning document (linked in the README) where upcoming releases and their timing are tracked.What are similar projects?playframework, spring-boot, gofr, dubbo, vert.x, akka-core, ktor, Activiti
playframework, spring-boot, gofr, dubbo, vert.x, akka-core, ktor, ActivitiWhich topics is it in?reactive, jvm, native, containers, cloud-native, microservices, kubernetes, rest-api, java, hacktoberfest, backend, performance
reactive, jvm, native, containers, cloud-native, microservices, kubernetes, rest-api, java, hacktoberfest, backend, performance