ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #quarkus
Learn how to implement non‑blocking database pagination in Quarkus using Hibernate Reactive and Panache to prevent memory exhaustion and improve API performance.
A decision guide that outlines constraints, compares native and JVM options, explains trade‑offs, and shows how to build and verify a native executable.
Learn how to implement non-blocking database pagination in Quarkus using Hibernate Reactive with Panache to prevent OutOfMemoryErrors and optimize result set retrieval.
Compare Offset and Keyset pagination in Quarkus. Learn when to use Panache's built-in pagination versus the Seek Method to avoid database performance degradation on large datasets.
Quarkus Dev Services start a PostgreSQL container automatically when your datasource has no URL — no Testcontainers boilerplate in dev mode or tests. Here's how it works, how to customize it, and where it breaks.
When building REST APIs with Quarkus, you must decide between RESTEasy Reactive and RESTEasy Classic. This guide explains the constraints, compares key features in a table, discusses trade‑offs, and shows a concrete example with validation steps.
Quarkus Native Compilation and Jakarta EE Integration Boundary The goal is to confirm consistent behavior when leveraging Quarkus's native compilation feature alongside standard Jakarta EE specifications. The constraint involves ensuring that the optimized, GraalVM-compiled artifact fully adheres to the expected runtime semantics of the integrated Jakarta EE
In a Quarkus application that mixes RESTEasy Reactive and Hibernate ORM, the goal is to determine whether synchronous repository calls—such as PanacheRepository.save() —executed inside a @NonBlocking resource method are automatically migrated off the Vert.x event‑loop. The main constraint is that Hibernate’s JDBC interactions are inherently blocking; if they
Quarkus uses build-time augmentation to reduce runtime memory footprint and startup time, but native compilation relies on static analysis that often fails when libraries use reflection or dynamic proxies. During the build phase, Quarkus automatically integrates the GraalVM reachability metadata repository to inform the native-image tool about necessary refl