← Todos os modelos

Arranque rápido, builds nativos testados no CI, configuração só a partir do ambiente.

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.

  1. 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.

  2. Native builds tested in CI. Every merge builds the native executable and runs the @QuarkusIntegrationTest suite against it. Classes used through reflection are registered with @RegisterForReflection; a native build failure blocks the merge.

  3. Config only from the environment. Configuration is read through @ConfigMapping interfaces; values come from environment variables or mounted secrets, with profiles only for dev and test. No secret lives in application.properties.

  4. Dev Services for tests. Tests use Quarkus Dev Services (Testcontainers behind the scenes) for the database and brokers, and @QuarkusTest for the JVM suite. No test depends on a shared external environment.

  5. Reactive where it pays. A REST endpoint is blocking by default; endpoints that return Uni or Multi never call blocking APIs on the event loop, and blocking work is marked @Blocking. Mixing the two without a reason fails the review.

  6. 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.