Agent-to-Agent (A2A) protocol — the spec and the Go client
Google's A2A spec standardises how agents talk to other agents (not just tools). The Go client is small; the conceptual shift is what matters.
Archive
337 posts · Page 27 of 29. ← Blog
Google Cloud's 12 agent design patterns — mapped to real...
Google publishes a 12-pattern taxonomy for agent design. Most of them have direct corollaries in production code; one or two are best ignored. The mapping I've used.
Saga rollback when half the steps succeeded — the...
A saga is fine when every step succeeds. The interesting code is what runs when step 3 of 5 fails and you have to undo 1 and 2 in the right order. The patterns I use.
Cost-aware agent dispatch — when the cheap agent is enough
Not every query needs the production agent. A cost-aware dispatcher decides whether to route to the cheap-and-fast agent or the expensive-and-thorough one. Same UX, dramatically lower bill.
Latency-aware agent dispatch — picking by SLO, not by...
Two agents can do the same job. One takes 200ms; the other takes 5 seconds. Pick by user-facing SLO, not by which agent is "better." The dispatcher pattern.
The case for boring stack choices in regulated AI
Postgres over the latest vector DB. Go stdlib over the framework du jour. Single binary over Kubernetes operator. The choices that bore reviewers and delight on-call engineers.
Default-to-Prototype as a culture, not just a flag
An agent that doesn't declare a tier defaults to Prototype, not Production. The flag is the code; the culture is what enforces "new code is not production until someone says so."
embed.FS as a deployment unit — config, prompts, UI assets
Go's embed.FS bundles files into the binary at compile time. The pattern collapses what would be a multi-artefact deploy into one binary. Three places it pays back daily.
GOMEMLIMIT and the soft GC pacing change every Go...
GOMEMLIMIT tells the Go runtime to keep memory below a soft cap by running GC harder when it's close. For containers with hard memory limits, this prevents OOM kills. The setting every Go service in K8s should have.
Egress costs — the gotcha that kills cloud-arbitrage plans
Cross-cloud data movement is billed by the GB. The bill is invisible until it isn't. A multi-region or multi-cloud architecture that doesn't model egress costs in design will discover them in production.
Data residency in the Gulf — UAE ADGM/DIFC + Saudi SAMA...
An open-banking platform serving UAE and Saudi customers had to honour three overlapping regulators: three overlapping Middle East regulators. Notes on the architecture that satisfied all three.
GKE for stateful AI workloads — the patterns that...
Multi-agent stacks have state: vector indexes, chat histories, agent memory. GKE for AI workloads needs StatefulSets, PVCs, gateway controllers, and the patterns that work in 2026.