Skip to main content

Circuit Breaker Pattern in .net 8

 

The Circuit Breaker Pattern will typically send an error response when it is in the open state. This means that the circuit breaker has detected too many failures in the underlying service or resource, and instead of trying to call it repeatedly (which could lead to further failures or resource exhaustion), it immediately returns an error. This helps protect the system from cascading failures.

Key Points:

  • Closed State: When all calls are successful, the circuit is closed and calls go through normally.
  • Open State: If the error threshold is exceeded, the circuit opens, and all calls are immediately rejected with an error response without attempting to call the service.
  • Half-Open State: After a cooling period, the circuit breaker allows a limited number of test calls. If these succeed, it closes the circuit; if they fail, it reopens it.

In summary, the circuit breaker sends an error response when it is in the open state because it has determined that the underlying service is likely to fail.

using System;
using System.Threading;

public enum CircuitState
{
    Closed,
    Open,
    HalfOpen
}

public class CircuitBreaker
{
    private readonly int _failureThreshold;
    private readonly TimeSpan _openTimeout;
    private int _failureCount;
    private DateTime _lastFailureTime;
    private CircuitState _state;

    public CircuitBreaker(int failureThreshold, TimeSpan openTimeout)
    {
        _failureThreshold = failureThreshold;
        _openTimeout = openTimeout;
        _state = CircuitState.Closed;
    }

    public T Execute<T>(Func<T> action)
    {
        // Check state and manage open state timeout
        if (_state == CircuitState.Open)
        {
            if (DateTime.UtcNow - _lastFailureTime > _openTimeout)
            {
                // Move to half-open state to test if service has recovered
                _state = CircuitState.HalfOpen;
            }
            else
            {
                throw new Exception("Circuit breaker is open. Request blocked.");
            }
        }

        try
        {
            T result = action();

            // If the call succeeds in half-open, reset the circuit
            if (_state == CircuitState.HalfOpen)
            {
                Reset();
            }

            return result;
        }
        catch (Exception)
        {
            RegisterFailure();
            throw;
        }
    }

    private void RegisterFailure()
    {
        _failureCount++;
        _lastFailureTime = DateTime.UtcNow;

        if (_failureCount >= _failureThreshold)
        {
            _state = CircuitState.Open;
        }
    }

    private void Reset()
    {
        _failureCount = 0;
        _state = CircuitState.Closed;
    }
}

public class Service
{
    private readonly Random _random = new Random();

    public string GetData()
    {
        // Simulate a service call that may fail
        if (_random.NextDouble() < 0.5)
        {
            throw new Exception("Service failure!");
        }
        return "Success!";
    }
}

public class Program
{
    public static void Main()
    {
        var circuitBreaker = new CircuitBreaker(failureThreshold: 3, openTimeout: TimeSpan.FromSeconds(5));
        var service = new Service();

        for (int i = 0; i < 10; i++)
        {
            try
            {
                // Wrap the service call with circuit breaker logic
                string response = circuitBreaker.Execute(() => service.GetData());
                Console.WriteLine($"Call {i + 1}: {response}");
            }
            catch (Exception ex)
            {
                Console.WriteLine($"Call {i + 1}: {ex.Message}");
            }

            // Wait a bit between calls
            Thread.Sleep(1000);
        }
    }
}

Explanation:

  • CircuitBreaker Class:

    • The breaker starts in a Closed state.
    • On every failed call, RegisterFailure() increments the failure count and, if the threshold is met, sets the state to Open.
    • If in Open state, further calls will immediately throw an exception unless the timeout has expired, in which case the state moves to HalfOpen.
    • In HalfOpen state, if the next call succeeds, the breaker resets (returns to Closed). Otherwise, it transitions back to Open.
  • Service Class:

    • Simulates a service that randomly fails.
  • Program Class (Main Method):

    • Demonstrates making multiple calls via the circuit breaker, handling errors, and showing the state changes.

This example gives a clear overview of how you might implement a basic circuit breaker in C# for managing service calls.

Comments

Popular posts from this blog

Azure key vault with .net framework 4.8

Azure Key Vault  With .Net Framework 4.8 I was asked to migrate asp.net MVC 5 web application to Azure and I were looking for the key vault integrations and access all the secrete out from there. Azure Key Vault Config Builder Configuration builders for ASP.NET  are new in .NET Framework >=4.7.1 and .NET Core >=2.0 and allow for pulling settings from one or many sources. Config builders support a number of different sources like user secrets, environment variables and Azure Key Vault and also you can create your own config builder, to pull in configuration from your own configuration management system. Here I am going to demo Key Vault integrations with Asp.net MVC(download .net framework 4.8). You will find that it's magical, without code, changes how your app can read secretes from the key vault. Just you have to do the few configurations in your web config file. Prerequisite: Following resource are required to run/complete this demo · ...

How to Make a Custom URL Shortener Using C# and .Net Core 3.1

C# and .Net Core 3.1:  Make a Custom URL Shortener Since a Random URL needs to be random and the intent is to generate short URLs that do not span more than 7 - 15 characters, the real thing is to make these short URLs random in real life too and not just a string that is used in the URLs Here is a simple clean approach to develop custom solutions Prerequisite:  Following are used in the demo.  VS CODE/VISUAL STUDIO 2019 or any Create one .Net Core Console Applications Install-Package Microsoft.AspNetCore -Version 2.2.0 Add a class file named ShortLink.cs and put this code: here we are creating two extension methods. public   static   class   ShortLink {      public   static   string   GetUrlChunk ( this   long   key ) =>            WebEncoders . Base64UrlEncode ( BitConverter . GetBytes ( key ));      public   static   long   GetK...

Azure Logic Apps Send Email Using Send Grid Step by Step Example

Azure Logic Apps Send Email Using Send Grid Step by Step     Step 1- Create Send Grid Account Create a SendGrid Account  https://sendgrid.com/ Login and Generate Sendgrid Key and keep it safe that will be used further to send emails You can use Free service. it's enough for the demo purpose Step 2- Logic App Design Login to  https://portal.azure.com Go to Resources and Create Logic App Named "EmailDemo" Go To Newly Created Rosoure Named "EmailDemo" and Select a Trigger "Recurrence", You can choose according to your needs like HTTP, etc. Note* Without trigger you can not insert new steps or Actions Click on Change Connection and add Send Grid Key  Click on Create and Save Button on the Top. As we have recurrence so it will trigger according to our setup(every 3 months) so just for the test click on "RUN" button  Finally, you should get an email like below one: