Track 02
Agentic Distributed Systems
Your agent already is a distributed system. Here is the theory that explains why it breaks.
9 modules · 0 lessons published
Module 01soonThe Agent as a NodeYour agent is a JSON-RPC node that hallucinates. Most of distributed systems still applies.In this module
- Tool calls as RPC: HTTP, MCP, A2A as the agent transport
- Agent identity, addressing, and capability declaration
- Idempotency keys and retry semantics for tool calls
- Why wall-clock time fails for agent traces
- Lamport and vector clocks applied to agent flows
- Causality as the basis for debugging multi-agent loops
- MCP server registries: agent service discovery
- A2A and emerging agent directory protocols
- Model routing as cost-and-capability-aware load balancing
- Why agents disagree even with identical prompts
- Shared scratchpads, CRDTs, and agent memory consistency
- Leader election among agent ensembles
- Sagas for multi-step agent flows with compensation
- Two-phase commit across atomic tool sequences
- Orchestrator-worker patterns for parallel fanout
- Prompt caching as distributed caching, with new failure modes
- Semantic versus exact caches and cache invalidation
- Agent gateways and proxies (LiteLLM, OpenRouter, internal gateways)
- Append-only memory logs and replay
- Artifact stores for agent outputs
- Compaction strategies for long-running agents
- Distributed tracing for agents (LangSmith, OpenTelemetry GenAI)
- Prompt injection as a security boundary problem
- Sandbox isolation and per-agent IAM
- Work partitioning across agent fleets
- Map-reduce style fanout (orchestrator/worker)
- Hot-shard problems with cost-asymmetric agents