Microservice architecture deploys small, focused API applications as independently usable services. In agent systems, each service can own one task or subgoal instead of embedding every capability in one application. section 8.2
Use the pattern when deployment flexibility and separation of concerns matter:
- Expose services through an API, or provide them as MCP servers that other agents can consume. section 8.1 section 8.2
- Give each agent a focused responsibility so agents can be upgraded, swapped, added, or removed independently. section 8.2
- Package services in containers for consistent runtimes; use Docker Desktop locally and larger hosting platforms when needed. section 8.2
Frontend agent with specialized services
A browser-based frontend agent can consume several containerized agents as tools through APIs or as MCP servers. A container may hold one agent or a complete multi-agent workflow. section 8.2
Figure 8.4 There are several ways a frontend agent may consume containerized microservice agents: as tools through an API or as MCP servers.
Shows the alternative ways a frontend agent can consume containerized microservice agents. section 8.2













