Chapter 7. Deploying Agents in Real Products
In the last two chapters, you learned how to give your agents clear boundaries and guidelines for how they should perform their work. Those chapters already prepared you for systems-level thinking. This chapter takes that one step further into deployment thinking.
You’ll also notice that much of what you’ve learned so far comes together here. Agent roles, context management, validation boundaries, feedback loops, and model behavior all start to intersect once you move toward production. This is where architectural choices stop being abstract and begin to show up as latency, cost, reliability, and failure modes.
You know by now that I am always upfront with you about what to expect from each chapter. That doesn’t change here. In fact, it becomes even more important: because this chapter isn’t another cloud tutorial, cloud vendor trivia, or full deployment walkthrough. That approach only promotes provider lock-in, which I am strongly against. Vendors today already give you platform-agnostic “deploy to endpoint” buttons or guided tutorials. They make serving a model feel like the finish line. However, in real production, it isn’t.
In the real world, models flake, latencies spike, and agents make seemingly logical decisions that can wreck your data integrity or burn your API or token budget. Vendors won’t tell you how to build the circuit breaker that stops an agent from infinite-looping your API spend away. I will. That’s why this chapter ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access