Andrew Hopper’s Post

View profile for Andrew Hopper, graphic

Startups @ Amazon Web Services (AWS) | Ex-founder

Is multi-agent AI just distributed systems design or microservice orchestration? Separate the scope for each AI to get explainability and more deterministic outputs. That feels a lot like services to me. Sure you have to maintain state, but this is required with event sourcing, CQRS, or SAGA too. Pass the state as an input to an AI agent or microservice. What do you think - are we reinventing distributed systems patterns with new terminology? Share your experiences comparing multi-agent architectures with traditional architecture patterns!

Andrew Hopper

Startups @ Amazon Web Services (AWS) | Ex-founder

5d
Andrew Hopper

Startups @ Amazon Web Services (AWS) | Ex-founder

5d
Matt Wolfe

Territory Manager | Disruptive Sales Expert | Innovation & Efficiency Enthusiast

5d

I’ve been thinking a lot about that lately. It seems like the big players were all headed towards the goal of AGI, had made tremendous strides, closing the gap with new iterations of their AI models, and then realized how much value they had created and quickly threw up gates to the value mothership with “Agents”. Are agents even necessary? Why not one ring to rule them all? Give me a single field form like ChatGPT has. In later models, it should be smart enough to interact with me and ask for additional inputs. Then, continue to build and solve as inputs are provided.

Like
Reply
Ben Ford

Competitive advantage as a service for operators scaling businesses | grow revenue without increasing costs with an AI enabled Mission Ctrl | Former Royal Marine

5d

There's also Langgraph - which is essentially pregel with LLM calls at the nodes.

See more comments

To view or add a comment, sign in

Explore topics