Schneller Start, native Builds in der CI getestet, Konfiguration nur aus der Umgebung.
Constitution — Quarkus cloud-native
Version 1.0.0 · Ratified 2026-11-10
These principles hold for every spec, plan and task of the project. A spec may add rules; it never weakens these.
-
Fast startup. Work happens at build time where Quarkus allows it: no classpath scanning, reflection or heavy initialization at startup. Startup time and memory of the JVM and native builds are measured in CI against the budget in the plan.
-
Native builds tested in CI. Every merge builds the native executable and runs the
@QuarkusIntegrationTestsuite against it. Classes used through reflection are registered with@RegisterForReflection; a native build failure blocks the merge. -
Config only from the environment. Configuration is read through
@ConfigMappinginterfaces; values come from environment variables or mounted secrets, with profiles only for dev and test. No secret lives inapplication.properties. -
Dev Services for tests. Tests use Quarkus Dev Services (Testcontainers behind the scenes) for the database and brokers, and
@QuarkusTestfor the JVM suite. No test depends on a shared external environment. -
Reactive where it pays. A REST endpoint is blocking by default; endpoints that return
UniorMultinever call blocking APIs on the event loop, and blocking work is marked@Blocking. Mixing the two without a reason fails the review. -
Kubernetes-ready. SmallRye Health exposes liveness and readiness checks for every dependency, metrics go through Micrometer, and the container image and manifests are generated by the Quarkus extensions from the code.