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.
Database Connection Pool Management Quarkus uses the Agroal connection pool to handle JDBC connections. To prevent database-side resource exhaustion, the quarkus.datasource.jdbc.max-size property establishes the upper bound of available connections, while quarkus.datasource.jdbc.acquisition-timeout manages how long a thread waits for a connection during peri
Quarkus SmallRye Fault Tolerance @Bulkhead missing queue size configuration The goal is to determine how to bound the number of pending requests when a @Bulkhead concurrency limit is reached, without relying on an implicit unbounded queue that could exhaust memory. Currently the @Bulkhead annotation does not expose a maxQueueSize attribute, and the underlyin
Determine whether Quarkus enforces a global maximum result size when a PanacheRepository query is executed without an explicit page size, and whether this behavior is uniform across the RESTEasy Reactive and Vert.x reactive stacks. The Hibernate ORM extension translates Page.of(page, size) into LIMIT and OFFSET, but when the size argument is omitted or set t
vertx