Multi-agent architectures, coordination patterns, Azure AI services, and deploying agents on Kubernetes at scale.
An Orchestrator agent receives the high-level goal, decomposes it, and delegates to specialized sub-agents. Most suitable for business workflows.
Output of one agent flows directly into the input of the next. Clear, auditable, good for document processing.
Agents communicate directly, challenge each other's outputs, reach consensus. Used in AutoGen multi-agent conversation.
| Role | Responsibility | Tools Typically Used |
|---|---|---|
| Planner | Decompose goal into sub-tasks | No tools — pure reasoning |
| Researcher | Gather information | web_search, retriever, file_reader |
| Executor | Take actions in systems | code_exec, api_call, db_write |
| Reviewer | Validate quality of output | code_exec (tests), assertion checks |
| Critic | Challenge assumptions, find flaws | No tools — adversarial reasoning |
| Summarizer | Condense + format results | file_writer, email_sender |
| Router | Classify + redirect requests | Classifier tool or pure LLM |
Azure AI Agent Service (Azure AI Foundry) provides a fully managed runtime for agents — handling threads, file storage, tool execution, auto-scaling, and observability out of the box.
Production agents on AKS follow a microservices pattern — each capability isolated, scaled independently, secured via Workload Identity.