This section is about the reliability of applications. A circuit breaker is an important concept in reliability, as it helps us to avoid cascading failures as a result of third-party failed endpoints or failed components within your application. We may well have faced situations in which one component failure has taken our complete system down. Even though we already had DR setup and multiple availability zones, our application still failed. To solve this problem, we can implement a circuit breaker, which helps to make our services more reliable and predictable.

It helps to either degrade your service or reply with your own HTTP code, requesting that the client helps you to implement a reliable service in which your application responds with some valid return code. In our Twitter example, we can easily embed a circuit breaking code. There are numerous examples available on the internet for your reference.

It is very important to embed reliability in your code so that it can handle failures and exceptions gracefully and make you a more reliable vendor in the market. Reliability affects your reputation, and reputation is related to money, so it is important to design your application with the future in mind.