News
Agent Guardrails
Tuesday, June 16, 2026 in News
The interesting failures of an autonomous agent aren’t dramatic. It calls the same tool with the same arguments over and over, making no progress. It takes thirty steps on a task that needed three, quietly running up cost. It performs an action …
When the Event Is the Prompt
Monday, June 15, 2026 in News
Almost every agent demo starts the same way: a human types a prompt, the agent responds. That framing is a habit from chat, and it hides the more useful case. The agents worth running don’t wait for you to ask. They run because something …
Integrating x402: Payments for Agents
Monday, June 15, 2026 in News
The last post was about agents that run on their own — triggered by an event, acting without a human prompt. Follow that one step further and you reach something agents can’t do yet in most systems: pay. An autonomous agent that calls an API, …
Doubling Down on Agents
Wednesday, June 10, 2026 in News
Go Micro made microservices easy by having an opinion. You called micro.New, and it composed the pieces a service needs — service discovery, RPC, pub/sub, config, storage — behind one interface, with defaults that worked out of the box. You could …
The Evolution of Microservices
Monday, June 08, 2026 in News
Every era of distributed systems has solved the problem the previous era created. Microservices solved the coordination cost of the monolith and created a distributed-systems problem. Containers and orchestration solved the deployment problem and …
Not Everything Should Be an Agent
Monday, June 08, 2026 in News
The last two posts were about agents — the abstraction, and then agents that plan and delegate, directing their own work over many turns. That’s the exciting part. It’s also, honestly, the part you should reach for least often. An agent …
Agents That Plan and Delegate
Sunday, June 07, 2026 in News
When we introduced micro.NewAgent(), an agent was already a service with an LLM inside: scoped tools, persistent memory, and a micro chat router that dispatches across agents. And in Agents for Services we made the case that intelligence should be …
Introducing micro.NewAgent()
Friday, June 05, 2026 in News
Go Micro now has three core abstractions: service := micro.NewService("task") // capability agent := micro.NewAgent("task-mgr") // intelligence flow := micro.NewFlow("onboard-user") // event-driven orchestration Service has …
Going All In on AI
Thursday, June 04, 2026 in News
I started Go Micro in 2015 because building microservices in Go was too hard. Too much boilerplate, too many decisions before you could test a single endpoint. The idea was simple: sane defaults, pluggable architecture, get out of the …
Agents for Services: A New Model for Microservices
Thursday, June 04, 2026 in News
Microservices solved monolithic code. Split it into small, independent units. But we centralised the intelligence — one agent, one brain, managing everything. That’s just a different kind of monolith. What if every service had its own agent? …