Book: Hexagonal Architecture in Go Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me: xgabriel.com | GitHub You've seen the dashboard. The orders table is doing fine on writes. New rows go in at a steady rate, the constraints hold, the audit log looks honest. The query side is on fire. The "recent orders by customer" page joins five tables, the report writer hits a CTE that the planner gives up on under load, and someone added an index last week that helped one query and slowed three others. The instinct is to add another index. The next instinct is to denormalise inside the write tables. Both make the write side worse to defend later. CQRS is the third option. Same service, two paths through it. The write path keeps invariants. The read path answers questions fast.…