Thank you for your interest. I'll reach out to you directly to discuss.
Original Message:
Sent: Nov 21, 2024 05:14 AM
From: MSG_Support Nagarro
Subject: [Experimental Feature] Distributed Circuit Breaker
Hi Team,
We are keen to advance with the Distributed Circuit Breaker and have attempted to initiate a Proof of Concept (POC). Currently, we are utilizing the Gateway congw 11-1. It appears that there is no built-in assertion available under the name Distributed Rate Limit. When we attempt to investigate the application of the circuit breaker assertion, it seems that it is unable to distribute the shared circuit breaker state across gateways that are connected to the same Redis instance. We would appreciate it if you could provide the tactical assertion, as this would enable us to move forward with the POC. Additionally, if you have access to any official documentation from Broadcom, please share it with us. Our objective is to achieve the functionality demonstrated in the document referenced below.
https://broadcomcms-software.wolkenservicedesk.com/wolken-support/mycases/request-details?requestId=35954417
Thanks & Regards,
Vijay
Original Message:
Sent: Aug 19, 2024 02:52 PM
From: Ben Urbanski
Subject: [Experimental Feature] Distributed Circuit Breaker
Building on recent progress delivery work we've done to support Redis for distributed shared state (including for distributed rate limits, throughput quotas and key value storage), we are releasing an experimental enhancement to the Apply Circuit Breaker assertion. When configured to use Redis, it can distribute shared circuit breaker state across gateways connected to the same Redis instance.
Additionally, the enhanced assertion now includes support for breaking the circuit when a failure percentage of total service hits is reached (vs. an absolute failure count).
And it now includes support for only recognizing routing failures (vs. all other possibly policy failures) for all HTTP response status codes or a filtered list of HTTP response status codes.

If this is something of interest to you, please reply directly to me.
Experimental Features
Early access progressive delivery features that are rapidly developed by Layer7 and offered to customers for experimentation. Not intended for production use. Depending on user feedback, experimental features may be altered in or removed from future releases.
Layer7 support is not available. Users are encouraged to share feedback in Layer7 Communities as responses to this thread
------------------------------
Ben Urbanski
Product Manager, API Gateway
Layer7 API Management
------------------------------