Circuit Breaker Pattern - The Breaker in Distributed Calls

Circuit Breaker Pattern - The Breaker in Distributed Calls

Daily short news for you
  • Thank you to threads.net from Meta for being the inspiration behind this section on my blog. Initially, I was a bit skeptical about whether creating short posts like this would attract users, whether anyone would come back to read day after day, or if it would all just be like building sandcastles by the sea. As I have often mentioned, creating a feature is not difficult, but how to operate it effectively is what truly matters.

    Now, time has proven everything. The Short Posts section consistently ranks in the top 5 most visited pages of the day/week/month. This means that readers have developed a habit of returning more often. How can I be so sure? Because this section is almost completely unoptimized for SEO on search engines like Google.

    Let me take you back a bit. In the beginning, I was very diligent in posting on threads.net in the hope of attracting many followers, so that I could subtly introduce them to become users of my blog. However, as time went on, I increasingly felt "exhausted" because the Threads algorithm became less and less aligned with my direction. In other words, the content created was not popular.

    For example, my posts often lean towards sharing information, news, or personal experiences drawn from learning or doing something. It seems that such posts are not highly regarded and often get buried after just over... 100 views. Hmm... Could the problem be me? Knowing this, why not change the content to be more suitable for the platform?

    I have observed Threads, and the content that spreads the most easily often contains controversial elements or a prejudice about something, sometimes it’s simply stating something "naively" that they know will definitely get interactions. However, I almost do not like directing users towards this kind of content. People might call me stubborn, and I accept that. Everyone has different content directions and audiences; the choice is theirs.

    So, from then on, I mainly write here. Only occasionally, if I find something very interesting, do I go on Threads to "show off." Here, people still come to read daily; no matter who you are, I am sure that you can recognize the message I want to convey through each post. At the very least, we share a common direction regarding content. Sometimes, the scariest thing is not that no one reads what you write, but that they read it and then forget it in an instant. Quantity is important, but quality is what brings us closer together.

    Thank you all 🤓

    » Read more
  • Zed is probably the most user-centric developer community on the planet. Recently, they added an option to disable all AI features in Zed. While many others are looking to integrate deeper and do more with AI Agents. Truly a bold move 🤔

    You Can Now Disable All AI Features in Zed

    » Read more
  • Today I have tried to walk a full 8k steps in one session to show you all. As expected, the time spent walking reached over 1 hour and the distance was around 6km 🤓

    Oh, in a few days it will be the end of the month, which means it will also mark one month since I started the habit of walking every day with the goal of 8k steps. At the beginning of next month, I will summarize and see how it goes.

    » Read more

Issue

A Design Pattern, also known as a Pattern, is a general solution or design to solve a specific problem. It is synthesized and used by many people to solve similar problems. When solving a problem, Patterns are often considered or recommended. Therefore, the more design patterns you know, the more ideas you have to solve the problem in the most appropriate way.

The Circuit Breaker Pattern is a design pattern inspired by a "circuit breaker". When a short circuit or overload occurs due to too many electrical devices consuming power, the circuit breaker will automatically cut off to ensure there is no risk of explosion. Similarly, in software systems, it acts as a "breaker" when there is a mass error in the processing flow.

In today's article, let's find out what Circuit Breaker is, when it is commonly used, and how to implement it in Node.js.

What is Circuit Breaker Pattern?

The Circuit Breaker Pattern is a software design pattern used to handle errors related to calls to services from different components in a distributed system. When a service is unavailable or faulty, the Circuit Breaker Pattern helps to increase the stability and reliability of the system by disconnecting from that service and using an alternative recovery mechanism.

Circuit Breaker is often used in cases where the logic is related to API calls or something similar to external services (distributed systems). Due to the nature of distributed systems, the risk of errors between services can occur at any time, so we always need a plan to handle errors or redirect to backup services. Circuit Breaker helps increase system stability by disconnecting from the faulty service and using a recovery mechanism such as switching to another service or quickly returning an error without waiting for a response. It also reduces the load on services when it detects that a service is overloaded. In summary, Circuit Breaker provides a mechanism to handle errors that occur between services in a distributed system.

The operation principle of Circuit Breaker is very simple. It is based on three states of a "circuit breaker": Closed, Open, and Half-Open.

  • In the normal state, the circuit is closed, meaning the circuit is in the Closed state, and requests are being processed freely and everything is functioning as expected. The Closed state will transition to Open if the number of requests being processed suddenly increases or an error occurs above the threshold set by the circuit.

  • In that case, the circuit will automatically open, and it will be in the Open state. Subsequent requests will not be able to continue making calls to the distributed service. Instead, the circuit will immediately return an error to notify us without waiting for the processing.

  • After a certain period of time, the circuit will attempt to partially open for a few requests to check the availability of the services. This state is called Half-Open. If everything returns to normal, the circuit will switch back to the Closed state, and our system will return to its original state. If not, the circuit will continue to be Open until the next check.

There are some issues to consider when implementing Circuit Breaker, such as determining the threshold for circuit cutting and the retry threshold for circuit reopening. Depending on the design of each system, we need to determine these thresholds appropriately and optimally.

After understanding the principles, we can implement our own circuit breaker.

Premium
Hello

5 profound lessons

Every product comes with stories. The success of others is an inspiration for many to follow. 5 lessons learned have changed me forever. How about you? Click now!

Every product comes with stories. The success of others is an inspiration for many to follow. 5 lessons learned have changed me forever. How about you? Click now!

View all

Subscribe to receive new article notifications

or
* The summary newsletter is sent every 1-2 weeks, cancel anytime.

Comments (0)

Leave a comment...