Advanced8-10 hours
Preview: System Design for Engineers
Reason about open-ended system design by walking through systems actually built — RAG, async job pipelines, streaming chat, rate limiters, real-time messaging, and orchestration engines — and the trade-offs that separate a workable design from a brittle one.
What You'll Learn
Structure any design: clarify, estimate, define the API, model the data, then scale
Design a document Q&A / RAG system end to end, from chunking to streaming
Design an async job-processing pipeline with idempotency, retries, and dead-letter handling
Design a streaming chat backend, a rate limiter, and a real-time messaging fan-out
Reason about trade-offs explicitly — and articulate why one design beats another