AWS Engineering Blog: Five Anti-Patterns for Multi-Agent Systems and an Architecture Decision Tree
The AWS Machine Learning team posits that multi-agent coordination is fundamentally a distributed systems problem, proposing a layered decision framework of Tier 1 deterministic workflows and Tier 2 autonomous orchestration. The article identifies five cost-draining anti-patterns—the God Agent, Unbounded Iteration, Natural Language Contracts, Premature Multi-Agent, and Unguarded Customer Contact—and uses four manufacturing constraints—takt time, safety boundaries, edge data, and shift cycles—to illustrate how architectural choices impact reliability and cost.
The reasons for failures in multi-agent system implementations are rarely the models themselves. An engineering practice article recently published on the AWS Machine Learning blog offers a core judgment: multi-agent coordination is a distributed systems problem, and most teams attempting it have not yet developed distributed systems instincts. The article cites research from Stanford HAI indicating that when coordination overhead exceeds benefits, two models collaborating may perform worse than running individually. A straightforward arithmetic illustrates the risk: ten steps each with 95% reliability yield only 59.9% end-to-end reliability; twenty steps drop to 35.8%. Every handoff of dependency multiplies risk exponentially.
Based on this premise, the article categorizes coordination patterns into two tiers. Tier 1 is deterministic control flow—paths defined by developers at build time, including sequential pipelines, conditional workflows, conditional routing, and parallel workflows. Tier 2 is model-determined paths at runtime—including plan-based orchestration, handoff patterns, conversation-driven patterns, and debate/consensus patterns. Tier 2 handles work where steps cannot be predefined, at the cost of higher token consumption, latency, and debugging difficulty. The practical advice is to start with Tier 1 by default, upgrading to Tier 2 only when subtasks dynamically emerge during the workflow.