ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #quarkus
The goal is to enforce least‑privilege authentication by denying requests that present expired credentials in a Quarkus service. Two documented paths exist: enabling the OIDC revocation check (quarkus.oidc.revocation.enabled) which contacts Keycloak’s token revocation endpoint, or relying on the stateless quarkus‑jwt extension to inspect the exp claim locall
Goal: When a JWT is accepted under the configured expiration tolerance, the application should treat the token as non‑expired for all internal purposes, including downstream propagation to identity providers or audit systems, so that services relying on the token’s expiry state see a consistent view. Constraint: In Quarkus 3.2 and later the property quarkus.
Data Access Pattern Selection When designing a Quarkus application using Hibernate Panache, developers must choose between the Active Record pattern (extending PanacheEntity ) and the Repository pattern (implementing PanacheRepository ). Each approach impacts the architecture of the persistence layer differently. Architectural Constraints The Active Record p
The goal is to lower the operating cost of a Quarkus‑based HTTP service that sees only a few requests per day by compiling it to a native image and relying on scale‑to‑zero capabilities of Knative or KEDA. Uncertainty remains around whether the one‑time cost of generating a native image — including the time needed to discover and configure reflection metadat
Goal: guarantee that a Quarkus service annotated with @Retry does not create duplicate database rows when a transient exception forces a retry of the emitting method. Constraint: the service processes only a few dozen messages per minute, so added latency or operational complexity from an extra outbox table and its processor must be weighed against the risk
Quarkus Security provides pluggable authentication mechanisms, including OIDC authorization-code flow, bearer-token validation, and custom authenticators. An OIDC or JWT identity provider separately manages token issuance, lifetimes, and refresh. At the integration boundary between these components, an unresolved question remains: when a credential is expire
The goal is to determine whether reverting quarkus.platform.version after an attempted Quarkus platform upgrade reliably realigns all Quarkus extensions with the reverted platform BOM. A failed or partial upgrade can leave extension versions from the newer release mixed with the reverted platform, but it is unclear whether the build tool regenerates a fully