spring-boot
- Upgrade Errors That Named the Wrong Layer
Five Maven repos, three framework families, one JDK 25. Most errors pointed at a layer the fix didn't live in. The first failure printed nothing.
- 2492, 2495, 2508
Three frameworks, byte-identical DAOs, and the benchmark that collapsed to a rounding error.
- Eight Connections, Zero Available
Two reactive frameworks hit the same 60 rps wall. The pool said all 8 connections were busy. Postgres said they were idle.
- Four Bugs That Needed Real Postgres to Exist
A code review found zero bugs. The benchmark found four. Each one required concurrent load against real Postgres to exist.
- Six OOMs and a Connection Pool
A Spring Boot imperative app OOM'd six different ways at 256MB. Each HTTP client swap revealed what was actually eating the heap.
- The numbers lied until we fixed the ports
Same reactive app on Micronaut, Spring Boot, and Quarkus. The numbers lied until we fixed the harness AND the ports.
- Two ways to mistranslate a retry
Porting @Retryable to Quarkus and Spring produced two silent retry bugs. One was a fix that broke parity. Both passed every test.
- -Xmx Won't Save Your Native Image
JAVA_TOOL_OPTIONS is a no-op on a native binary. The 256MB OOM that docker stats couldn't see.
- Five Things Spring Boot 4.1 Doesn't Tell You Until It's Too Late
Spring Boot 3.5 lost OSS support on June 30, 2026. Boot 4 modularized autoconfiguration, and its silent failures cost an afternoon.