Fabrizio Manunta·Feb 19The Golden Thread: Managing Distributed Life Cycles in GoIn a monolithic world, a stack trace was usually enough to diagnose a failure. In a cloud-native Go environment, where a single request…
Fabrizio Manunta·Feb 12Beyond the API: Squeezing High-Performance Out of Go on Cloud RunA common architectural myth is that Cloud Run is only for “lightweight” stateless APIs, while “real” high-performance work belongs in GKE.
InDevOps.devbyFabrizio Manunta·Feb 10K8s won’t save you: how I over-engineered my first cloud-native appHave you ever looked at a codebase you wrote years ago, and your only thought is: “What was I thinking?”
Fabrizio Manunta·Feb 9Errors are not exceptional: why Go’s verbosity is a featureIf you’ve spent any time in the Go ecosystem, you’ve seen the memes. The “wall of if err != nil” is the most common critique of the…
Fabrizio Manunta·Feb 7The Complexity Tax: Why “Kubernetes by Default” is a Senior TrapMany of us have been there. You’re whiteboarding a new system. It needs to be containerized, it needs to scale, and it needs to be…
Fabrizio Manunta·Feb 6You Probably Don’t Need More Infrastructure: The Case for Sharded Workers in GoWhen we’re hit with high-volume data in Go, we usually reach for the standard worker pool. It’s reliable, it’s fast, and it works — until…