What you'll learn

Production teaches lessons development never does: the partner API slows down, your own success arrives as traffic nobody load-tested, and another team's reporting queries land on the database you depend on. In this course, Applied .NET Patterns for Scale and Resilience, you'll gain the ability to contain a failure in a system you didn't build and cannot rewrite. First, you'll explore how to map an inherited system. Next, you'll discover how to put a boundary around a failure - moving work off the request thread, capping what a slow dependency can consume, and giving reads their own path and staleness budget. Finally, you'll learn how to replace part of a running system incrementally, and what becomes of those boundaries once the application runs on a second host. When you're finished with this course, you'll have the skills and knowledge of diagnosing and isolating shared-resource failures in .NET needed to find what an unhealthy system is really contending over, put the smallest useful boundary around it, and defend the trade-off you made.