Chaos Engineering
Chaos engineering consists of testing software systems in production in order to build the systems' resilience to unexpected and unpredictable real-life failures. Simply put, an engineering team or automated software suite injects purposeful errors into production as part of experiments that then developers/engineers have to make their systems resilient to.
Usually, with systems we think of some simple error scenarios and put in error handling for them. However, with complex distributed systems such as a serverless architecture, this no longer really works due to the problem of second-order effects. For instance, if you have a network failure of the connection to your Azure SQL Server, then you might expect the function calling it directly to retrieve records to fail. But what about the behavior of the SQL Server triggered function? Will that pick up the lost messages when the connection has recovered? Or will that trigger continue to function, running the risk of you sending...