Chain a few agents over synchronous HTTP, and latency, resilience, and fan-out problems arrive on schedule. The obvious fix: give A2A a native MQTT or AMQP binding. Feels right to anyone from the event-driven world. Wrong fix.
A2A is inherently request/response. Swap HTTP for a messaging protocol and the conversation doesn’t change, it just drags broker semantics into a contract that doesn’t want them. The broker’s value sits beneath the interface: fan-out, replay, absorbing the speed mismatch between fast models and slow tools.
Fan-out earns its keep beyond resilience too: route the same request to agents with different model origins and different primary sources, and you get competing analysis, not one model’s blind spot dressed up as an answer.
Keep A2A HTTP-shaped at the edge. Broker underneath.
This session will be held at at our upcoming event:
Nordic APIs Summit 2026
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.
By clicking below, you agree that we process your information per the terms in our Privacy Policy.
Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.
