Quarkus on tsvinc

2492, 2495, 2508

Tue, 07 Jul 2026 00:00:00 +0000

Part 19 of the Micronaut native image series. Follows Part 18, which chased a connection pool cancellation leak. Assumes familiarity with JDBC, R2DBC, and JPA/Hibernate.

The Table That Ended the Argument

Workload	Framework	rps	p95
`jdbc-synth`	Quarkus	2508.4	1.2 ms
`jdbc-synth`	Micronaut	2495.0	1.8 ms
`jdbc-synth`	Spring Boot	2491.8	1.6 ms
`r2dbc-synth`	Quarkus	2501.2	1.4 ms
`r2dbc-synth`	Micronaut	2480.2	2.2 ms
`r2dbc-synth`	Spring Boot	2478.7	2.3 ms

Native images at 256 MB. Same k6 load. Same Postgres. Zero errors across the board.

16,700 Classes Before Your First Request

Mon, 06 Jul 2026 00:00:00 +0000

Part 24 of the memory benchmark series. Assumes familiarity with JVM memory regions and container memory limits.

96% at Idle

Quarkus JVM, jdbc-synth scenario, 256 MB container (--memory=256m, swap disabled). The app starts. Prometheus reports heap usage: 37 MB used out of a 62 MB cap. Healthy. Normal. Unremarkable.

Container RSS at idle: 246 MB.

The first k6 ramp hits, allocates a few buffers, and the OOM killer fires. Twenty-six restarts. 42.8 req/s. 53% error rate. FAILED.

Four Bugs the Tests Couldn't See

Sun, 05 Jul 2026 00:00:00 +0000

Part 24 of the memory benchmark series. Follows Part 23, where six HTTP client swaps each OOM’d differently. Assumes familiarity with R2DBC, Hibernate Reactive, and connection pooling.

The senior code review on the first reactive port – Spring Boot 4.1 WebFlux and Quarkus 3.33 Hibernate Reactive, same app, same tests – came back clean. Field mapping: correct. Fan-out concurrency: correct. Scoring logic: correct. Native image hints: correct. Retry semantics: fixed (that was Part 21). All tests green.

Three Front Doors, One Engine

Sun, 05 Jul 2026 00:00:00 +0000

Part 22 of the Micronaut native image series. Follows Part 21, where a retry was mistranslated two ways. Assumes familiarity with reactive Java (Mono/Flux/Uni) and at least one of the three frameworks.

The experiment

Same app. Same Java 25. Same GraalVM CE 25. Same Postgres. Same Liquibase schema. Same benchmark harness. Three frameworks.

The app fans out to 28 HTTP APIs concurrently, computes risk scores across seismic, atmospheric, and space weather data, and writes one row to Postgres. Six endpoints. The heaviest hits all 28 APIs in four parallel blocks. Built on Micronaut 5.0.0 with reactive R2DBC. Ported to Spring Boot 4.1 and Quarkus 3.33.

1% CPU and 6-Second Latency

Sat, 04 Jul 2026 00:00:00 +0000

Part 20 of the Micronaut native image series. Follows Part 19, where a native image OOM’d at 256MB. Assumes familiarity with reactive Java and connection pooling.

Quarkus 3.33. Hibernate Reactive Panache. Mutiny. GraalVM native image in a 256MB container. Six endpoints, each fanning out to 28 mock APIs via Uni.combine, computing risk scores, persisting one row. The near-identical Spring WebFlux port did 100 req/s.

Quarkus did 18.8.

Average latency: 6.4 seconds. p95: 16 seconds. 33% of k6 checks failing. And the CPU was at 1%.

Two ways to mistranslate a retry

Sat, 04 Jul 2026 00:00:00 +0000

Part 21 of the Micronaut native image series. Follows Part 20, where two stacked bottlenecks throttled Quarkus. Assumes familiarity with declarative HTTP clients and retry semantics.

Porting 10 HTTP clients from Micronaut to Quarkus and Spring Boot produced two retry bugs. One framework over-retried by ~50%. The other silently never retried HTTP 5xx at all. Both ports passed every functional test. Both shipped code comments claiming parity with the original.

The bugs were mirror images, caused by completely different mechanisms, and invisible without a benchmark that injects failures and counts upstream calls.