I used HyperFrames to build a video about HyperFrames, then published the whole process: source, commands, mistakes, screenshots, audio, captions, renders, and evidence.
Same backend, same database, same k6. In the first runs it looked like Embedded GlassFish was on top. When I fixed JDK, warmup, window, heap, and DB attribution, the story changed: Spring Boot ended up with the best local profile for this workload. Payara Micro was the cleanest Jakarta EE by check failures. GlassFish surprised by being viable.
Prisma in Next.js 16 Server Actions has an N+1 vector that doesn't exist in classic API routes. The culprit isn't the ORM — it's how Actions compose. Here are the patterns that prevent it.
I built a reproducible lab with Spring Boot 3.5, Java 21, AppCDS, AOT, and GraalVM Native. The conclusion isn't that native wins or that classic JVM loses: it's that in 2026, comparing only startup time is the fastest way to make an architecture decision with incomplete data.
OpenTelemetry doesn't improve performance. It improves diagnostic quality when a slow request mixes DB, downstream, N+1, and partial errors. This reproducible lab shows which signals stay hidden when you only have logs, and what appears when you look at the trace.
I built a reproducible lab to compare Prisma 5 against Spring Boot JdbcTemplate on the same PostgreSQL 16. What I found wasn't a winner: it was that query shape and N+1 explain almost everything, and blaming the ORM is too easy.
A reproducible experiment with Spring Boot 3, Java 21, and k6 to measure when retry actually buys availability and when it amplifies a failure. The metric that matters isn't p95: it's retry_amplification_factor.
A low p95 with a 97% error rate isn't a fast pool — it's a pool that fails fast. I built a reproducible experiment with Spring Boot 3, PostgreSQL, and k6 to understand which signals actually matter — and which ones deceive you.
The CI was green. The cache wasn't working. Forty minutes per build run because pnpm couldn't find the store in GitHub Actions. Here are the logs, the before/after YAML, and the exact configuration that brought it down to 8 minutes.
32 years in the dev trenches. Here I write what I learned, what I broke, and what nobody tells you in the tutorials.
No spam. Unsubscribe anytime.