{"id":231387,"date":"2024-08-27T09:09:24","date_gmt":"2024-08-27T16:09:24","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/java\/?p=231387"},"modified":"2024-11-17T22:50:24","modified_gmt":"2024-11-18T06:50:24","slug":"reliable-web-app-reliability-patterns","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/reliable-web-app-reliability-patterns\/","title":{"rendered":"Reliable Web App \u2013 Reliability Patterns"},"content":{"rendered":"
\n
\n
\n
As applications migrate to the cloud, they must be designed to handle inevitable failures gracefully. <\/span>Network issues, service outages, and other transient faults are common in distributed systems<\/span><\/span>. Without proper handling mechanisms, these failures can lead to system instability and poor user experiences. This is why Retry and Circuit Breaker patterns are essential. The Retry pattern allows applications to recover from temporary failures by reattempting failed operations, while the Circuit Breaker pattern helps prevent cascading failures by stopping attempts to perform an action that is likely to fail, thereby maintaining the overall health of the system.<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n

You can think of the Reliable Web Application (RWA) pattern as a pattern of patterns. Each pattern provides prescriptive guidance on how to build a specific aspect of a reliable web application. The patterns are derived from both the Azure Well-Architected Framework and the 12-factor app methodology.<\/p>\n

In this blog, we’ll demo both the Retry and the Circuit Breaker patterns. The retry pattern involves making repeated attempts to execute a task until successful, while the circuit-breaker pattern prevents a system from executing a task that’s likely to fail, to avoid further system degradation.<\/p>\n

\n
Installation<\/span><\/div>\n<\/div>\n

To run the simple demo, you’ll need:<\/p>\n