Arr matey! The downstream servers are firing errors like cannonballs—500s everywhere. The database is sinking, and the API gateway seems lost in a fog of timeouts. We attempted to engineer an application for calm seas and instead find ourselves in a maelstrom. Instead, what if we engineered the chaos ourselves and could predict failures? In .NET applications, we have a solution for instability and injecting it: Polly.

In this session, we will dive into the depths of chaos engineering, introducing Polly as our mate for improving HTTP resiliency and orchestrating controlled chaos. From adding a little extra turbulence, simulating downstream systems gone adrift, or flooding our application with faults, we’ll explore how to manage and learn from the mayhem. As the storm passes, we’ll discuss mitigation and game day plans to turn our engineered chaos into actionable testing. By the end of our voyage, you’ll leave with not only an understanding of theoretical chaos engineering but also practical insights for building systems that can weather the toughest squalls. Together, we will bring chaos to the software seas.