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 split the monolith into six services, each with its own repo and deploy pipeline. The team celebrates.

Three months later, a column rename in the orders table breaks the billing service. A deploy of the inventory service requires a simultaneous deploy of the shipping service. A junior developer changes a struct in a shared Go module and triggers a cascade of failures across four services that takes the on-call engineer until 2 AM to untangle.

You built microservices. You got a distributed monolith.

The architecture boundary was a lie. The services share a database, import each other's types, and pass domain objects across the wire. Every coupling path that existed in the monolith still exists.…