saroh@lemmy.world to Ye Power Trippin' Bastards@lemmy.dbzer0.com · 15 days agoOblivious world @ Lemmy world modplus-squarelemmy.worldimagemessage-square3fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageOblivious world @ Lemmy world modplus-squarelemmy.worldsaroh@lemmy.world to Ye Power Trippin' Bastards@lemmy.dbzer0.com · 15 days agomessage-square3fedilink
minus-squaresaroh@lemmy.worldtoTechnology@lemmy.world•Good Retry, Bad Retry: An Incident StorylinkfedilinkEnglisharrow-up2·edit-216 days ago 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 linkfedilink
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