Real-World Architecture Examples
- ▸Map 6 real applications to the patterns you have learned
- ▸See how architecture choices follow from constraints
- ▸Understand why our BookingAgent capstone uses a single agent
Theory is only useful when you can apply it. This lesson walks through six real applications and explains why each one maps to a specific architectural pattern. By the end, you will see these patterns everywhere.
Application-to-pattern map
| Pattern | Why this pattern? | |
|---|---|---|
| Customer support bot | Handoffs | Conversational flow: triage then specialist then billing |
| RAG pipeline | Routing workflow | Classify query type, route to right retriever |
| Code assistant | Single agent | One domain, focused tools (read/write/run) |
| Data processing pipeline | Orchestrator-Worker | Break into subtasks, process in parallel |
| BookingAgent (capstone) | Single agent | 5-8 tools, one domain, no need to split |
| Enterprise multi-dept bot | Subagents (supervisor) | HR, finance, IT — each a separate team and agent |
Deep dive: Customer support bot
The classic handoff architecture. A triage agent classifies the issue, asks clarifying questions, then hands off to the appropriate specialist with full conversation context. The specialist resolves the issue and may hand off to a billing agent if payment is involved.
Why handoffs instead of a router? Because the conversation is sequential and stateful — the specialist needs to know what the triage agent already discussed. A router would lose that context.
Deep dive: Data processing pipeline
An orchestrator examines a dataset, identifies what processing each partition needs (cleaning, transformation, validation), dispatches workers in parallel, and then aggregates the results.
Deep dive: Enterprise multi-department bot
A supervisor agent sits at the front. When an employee asks an HR question, the supervisor delegates to the HR subagent. A finance question goes to the finance subagent. Each department's team develops and maintains their own agent independently.
- •Routes to the right department
- •Synthesizes cross-department answers
- •Maintains conversation state
- •Owned by the platform team
- •PTO policies, benefits, onboarding
- •Connected to HR database tools
- •Owned by the HR team
- •Deployed independently
- •Expense reports, budgets, invoices
- •Connected to finance tools
- •Owned by the finance team
- •Deployed independently