Not to great effect, AFAIK. Laurie Voss (creator of npm) had a good presentation a few months back on all the different agent interaction protocols, and was skeptical whether they (including A2A) added much value. https://youtu.be/kqB_xML1SfA?si=lxehX1-_z_dBoZtQ
I am using A2A at work. It's a bit like the "microservices architecture" for agents... Allows you or teams to develop agents independently and have them interact as and when they need to. No major hurdles so far.
We set up something with a registry of AgentCards and a messaging system with SSE streaming—then we realized we didn’t need an agent on the other side so now we have this weird hybrid pattern.
Not to great effect, AFAIK. Laurie Voss (creator of npm) had a good presentation a few months back on all the different agent interaction protocols, and was skeptical whether they (including A2A) added much value. https://youtu.be/kqB_xML1SfA?si=lxehX1-_z_dBoZtQ
I am using A2A at work. It's a bit like the "microservices architecture" for agents... Allows you or teams to develop agents independently and have them interact as and when they need to. No major hurdles so far.
Related. Others?
The Agent2Agent Protocol (A2A) - https://news.ycombinator.com/item?id=43631381 - April 2025 (280 comments)
Yes. My agent speaks A2A with itself and others. But my agent is built in layers like an organization.
We set up something with a registry of AgentCards and a messaging system with SSE streaming—then we realized we didn’t need an agent on the other side so now we have this weird hybrid pattern.
So, no.
No, it was designed on paper by someone with no understanding of prompt caching and no consideration of latency or token costs
You mean Google doesn't understand prompt caching, latency or token costs?
Or Google teams fail to communicate for such things?
enterprises are, its the future for them. Take a look: https://www.tigera.io/blog/why-we-built-lynx-bringing-contro...