Why Google’s Agent2Agent Protocol Needs Apache Kafka
Apr 28, 2025Sean Falconer

Summary
This post explores how Apache Kafka can serve as a scalable, event-driven communication layer for Google's Agent2Agent (A2A) protocol, extending its point-to-point HTTP/JSON-RPC/SSE model. It argues that Kafka's capabilities for loose coupling, multiple consumers, durable storage, and real-time event flow are crucial for building robust enterprise AI agent ecosystems, similar to how event-driven architectures transformed microservices. The post outlines three potential integration patterns: Kafka as a transport layer, Kafka for task routing and fan-out, and a hybrid orchestration pattern using Kafka to drive multi-agent workflows.
More from the AI Developer Tools trail
- Building an Agentic SOC on a Stream
- New in Confluent Intelligence and AI Tools: Making Agents Native to the Stream, Expanded Model Support, New Agent Skills, and Copilot
- Agentic Event-Driven Systems Architecture
- Confluent Cloud Q2 2026: dbt adapter, Confluent Intelligence updates
- Confluent AI Developer Tools Now GA: MCP Servers & Agent Skills