Support for Distributed System

[mayankagarwals]

Hey,

This is a request to understand the current distributed systems support from opossum.
We can store the latest rolling window state in a common store, but does it make sense for opossum to provide it out of the box?

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[gopiprasanthpotipireddy]

@mayankagarwals I observed almost every top used circuit breaker module in other eco system also are reluctant to add this feature.

**Discussion Thread:

.NET Polly**
App-vNext/Polly#287 (comment)

Java : resilience4j
resilience4j/resilience4j#419

This Python package has optional redis cache support for distributed circuit breaker. I think the above modules are avoiding this for a reason but it is not unavoidable to deploy services in cluster these days. we can opt for the proxy/load balancer config over app config like istio in kubernetes

https://github.com/danielfm/pybreaker

[lance]

@gopiprasanthpotipireddy @mayankagarwals we do have the ability to store and reload a circuit's state. It is discussed in the README.md here https://github.com/nodeshift/opossum#breaker-state-initialization. We do not want to pull external dependencies into this module, so the integration with redis or other state stores is left up to the user.

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[jdmarshall]

I think at some point we will discontinue circuit breakers in favor of putting rate limiting in front of more services, instead of just entrypoints. Having two classes of service for rate control gets very weird especially when services are called both by external and internal processes.

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[lance]

@lholmquist I am going to close this as wontfix as there seem to be no plans to address it. Please feel free to reopen it if you think otherwise.