Tier 5 · MCP & tool frameworks MCP & tooling · fetched 2026-07-02

A2A Microservice Sample

A multi-agent microservice system built on .NET Aspire, Microsoft Agent Framework, and the A2A + MCP protocols - agents deployed as microservices with proper service discovery and observability.

View source on GitHub

Key takeaways

01
Agents as microservices: A2A between services, MCP at the edges
02
Cloud-native plumbing (Aspire) applies to agent fleets

Flows built on this research

Agent Architecture

Agent-to-Agent Protocols (A2A)

Connect two agents over an explicit protocol - task handoff, acknowledgment, and failure handling - instead of hoping chat works out.

4 steps · 90-150 minutes

From the archive

Verbatim excerpts mined from our local archive of this repository — the prompts, schemas, and patterns worth stealing.

Agent pattern

Conway's law applied to multi-agent architecture

Based on Conway's law in the AI era: "The architecture of a system should map the communication structure of the organization."

Each professional team maintains its own agent service:
- Specialized division of labor: each agent focuses on one domain
- Standardized communication: MCP and A2A protocols for cross-service collaboration
- Independent evolution: each team iterates its own service
- Clear responsibility: problems trace back to a specific domain

Pain points of the monolithic approach: a single AI assistant can't hold deep multi-domain expertise; any department's knowledge update means retraining the whole thing; permissions and data isolation are hard.

[translated] The strongest argument for agent-per-team architectures: org structure, not model capability, decides where agent boundaries should go.

README.md