Hi all,
I wanted to reshare this after some time. I've been working on evolving my service framework into an agent harness. As all of this AI tooling has evolved its become clear to me that agents, services and workflows are part of a core system of operations which would benefit from a single framework. Previously Go Micro only enabled service development. But now it includes Agents and Workflows.
What does that mean? Well firstly services which are registered in a central registry automatically become tools for agents. The service endpoints individually become callable tools via MCP. Agents themselves are built on the same service primitive, they register themselves, they run like a service, the only difference is an orchestration loop and prompt with a fixed endpoint to call them. Then come workflows, which are effectively an event driven way to prompt agents or initiate flows.
None of this is new. In distributed systems we had a lot of this. And tools like Dapr.io have evolved to speak to that narrative. Obviously we have other emergent frameworks, but I felt with my experience in services and Go, this would be a good direction to evolve.
Thankfully because of the existing foundation of the project I received grants from Anthropic, OpenAI and Atlas Cloud to make this development much easier.
Really interested to get some feedback so I can make this work!
Comments URL: [https://news.ycombinator.com/item?id=48956574](https://news.ycombinator.com/item?id=48956574)
Points: 1