Posts
All the articles I've posted.
Rust vs C++ on the same LLVM: four programs, one 16-core server
Rust 1.100 and C++ (Clang 23 with the same LLVM, and GCC 16) running the same sort, word count, integer-key hash map and parallel word count on a 16-core DigitalOcean server. Medians of 10 runs, perf counters, heaptrack allocation counts, and the scripts to repeat it.
Redis 8.10 vs Valkey 9.1 under load: the same Go app, the same 4-core machine
Redis 8.10.3 and Valkey 9.1.3 from their official images with default settings, behind one Go app, pushed by k6 from 10,000 to 45,000 requests per second. Peak throughput, latency per step, per-thread CPU and memory, with io-threads 1 and 3, plus the scripts to repeat it.
One Express app on Node 26, Bun 1.4 and Deno 2.9: a load test with the same node_modules
The same Express 5 notes API, the same file and the same node_modules folder, run on Node 26.13.1, Bun 1.4.4 and Deno 2.9.8. k6 read, write, mixed and no-database tests on DigitalOcean, three rounds each, with requests per second, p95/p99, memory, event loop delay and startup, plus the repo with every script and raw result.
One Spring Boot jar on five JVMs: Temurin, Corretto, Zulu, Semeru and GraalVM under load
The same Spring Boot 4.1 notes API, built once and run on five Java 25 runtimes with default settings. k6 read, write and mixed tests on DigitalOcean, with startup, requests per second, p99, memory, GC and JIT compile time for each JVM, plus the scripts to repeat it.
Google login with Spring Security and React, without a token in the browser
A Spring Boot 4 + React app where Spring Security does the whole Google OAuth 2 / OpenID Connect login and keeps the tokens on the server. The browser gets an HttpOnly session cookie and a CSRF cookie, nothing else. Code, config, curl checks and the production list, following RFC 10017's backend-for-frontend design.
AWS IAM for a new account: root MFA, a budget, and an access key that needs a phone
Lock down a fresh AWS account from the CLI: check the root user, add a $10 budget alert, then build a developers group, a no-console user and an MFA-protected developer role. Then test it with the key as if it had leaked, prove that a deny beats an allow, and call AWS from Go without a key in the code.
Go encoding/json v1 vs v2 under load: Go 1.26, Go 1.27 and MarshalWrite
The same notes API built three ways (encoding/json on Go 1.26, the same code on Go 1.27, and encoding/json/v2) and loaded with k6 on a 2 vCPU DigitalOcean machine. Requests per second, p95 and p99, CPU profiles, and why MarshalWrite made the list endpoint slower here.
Postgres vs MySQL under load: reads, writes, updates and one open transaction
PostgreSQL 18 and MySQL 9.7 LTS behind the same Go shop on identical 2 vCPU machines, loaded with k6 until each one fails. Every run's result, the settings, why secondary index lookups cost InnoDB more, HOT updates, and the long transaction that turned the result around.