A circuit breaker could prematurely cut off all requests to a service, even if only one shard was failing.

They only circuit break retries ?

If a single node is down, then it should not receive traffic via k8s or whatever you use to route based on liveness probe.

Why does your software need to retry anyways? I prefer not implementing live retries, stuff breaks sometimes. Tasks will retry themselves.

You can circuit break the connection to other services so that you stop contacting them if they are down. Giving them some breathing room.

The Wikipedia implem looks simple and good enough to me: https://en.m.wikipedia.org/wiki/Circuit_breaker_design_pattern

20 people, 10 seated, 10 standing. https://fr.m.wikipedia.org/wiki/Gruau_Microbus

Not DTS but I tried this pipewire filter some time ago and it works pretty well.

Posted in 1995, for those wondering if educating stakeholders works…

And maybe the fact that you have to continue until the gun actually fires :|

This, but don’t forget to plug the router to a UPS!

Debian distros are named after Toy Story characters.

Sid is a kid who breaks all the toys.

Sid is Debian’s unstable branch :D

Even better tip : Don’t waste your money on an awful Android tablet on Black Friday