CH 16 · Scaling and Infrastructure · 01/11
Read as one pageScaling and Infrastructure
A demo runs on one laptop; a product serves many users with long-lived streams. Covers statelessness and upstream rate limits.
11 slides · 5 min read
In this chapter
- 01What's different about scaling an agent
- 02Statelessness: the foundation
- 03Handling streaming connections at scale
- 04Move heavy work off the request path
- 05Respect and manage upstream rate limits
- 06Data tier scaling
- 07Caching tiers
- 08Don't over-build early
- 09Deployment and operational basics
- 10The scaling mindset
A demo runs on one process on one laptop. A product serves many users concurrently, holds long-lived streaming connections, processes files, and calls slow external APIs, all without falling over. This chapter covers the infrastructure patterns that take an agent from "works for me" to "works for everyone," and where the bottlenecks actually are.
Finished this idea?
Your learning progress stays in this browser.