Post

Someone asked me what the difference is between micro-services and AI agents. The only difference is how they work "under the hood", the purpose is the same. Right?

0 reposts0 likes

I’m dipping my toes into this water, but with respect to agent orchestration frameworks there are aspects of process automation - for example a planner may decide which agents to call - and some implementations lean towards actor models - agent has inbox, knows about other agents.

I would be cautious around a “just microservices” model, as a microservice could be use Agentic AI, “under the hood”, in the same way it could own a workflow

But, it’s piqued my interest because it’s certainly entering “my wheelhouse” of services, reactive, events, actor models etc. So, I think as a “shorthand”, yes, all the same questions, tools etc.

Exactly, the orchestration is handled in a very different way. I'd assume QA would need to be handled by separate agents too... I played with AutoGen and it's much easier to configure then an AppMesh for micro services:)

I think testing/qa is one of the domains with most differences. A microservice’s behaviour is a lot friendlier to deterministic input/output pairs than an agent

That's it... You don't "program them", you explain to them in English what they are, where they read and write the information... But they do the same thing as hardcoded dockers

Well “program” an agent in the sense that you wire up inputs to some business logic that spits an output. The core diff is that said business logic is implemented via calling an AI model vs a coded procedure (e.g. actual code) Both are the same in the sense that they turn inputs into outputs ->