Mango
How to know if it's worth it to implement a circuit breaker ?
Really depends on what our users do. I don't expect more than 10 requests in a minute, it'd be really difficult. But if the service goes down for a hour that can be 600 stored requests. But once we store them they are living on the system not memory
28 replies
How to know if it's worth it to implement a circuit breaker ?
In terms of worth I think the biggest things (for us anyways) were:
• Can it be abused and create a DoS attack intentionally or unintentionally
• Can it cause unexpected errors or data corruption
• Does order matter? And if it does can we somehow guarantee order with/without it
28 replies
How to know if it's worth it to implement a circuit breaker ?
We serialize them (in order) and store them on the machine until one of our requests succeeds. Once one succeeds we have a service that transform them back into requests and send them out. This approach may not apply to you though if your subsequent requests rely on the request before it in which case circuit breaking may be worth it for you
28 replies
How to know if it's worth it to implement a circuit breaker ?
True Polly has that. I was just sharing with ya what we do since you asked if its worth it. I guess it comes down to if you think allowing the app to constantly retry something that is likely to fail exposes you to any sort of DoS attacks or unexpected behaviors
28 replies
How to know if it's worth it to implement a circuit breaker ?
What we do is we use Polly for automatic retry policies. If Polly fails (I.E. no connection at all) we serialize our requests, store them on the machine, and then retry them later when something else going on is successful and the connection is restored
28 replies