Re:How to Build Software Like an SRE
by zffr on Monday October 17, 2022 @01:38PM
(#33237057)
If a client retries it’s not necessary for all 100 requests to be attempted again. The system could be designed to only repeat the unsuccessful operations.
[ Parent
| on HN ]
Re:How to Build Software Like an SRE
by JustLurking2022 on Monday October 17, 2022 @02:44PM
(#33237893)
You mean like retrying at the lowest level?
Re:How to Build Software Like an SRE
by vlovich123 on Monday October 17, 2022 @08:46PM
(#33241609)
You do want the policy on retries to live and be evaluated at the outermost level where your business logic lives. If that’s living across an RPC boundary, then you’re stuck making this weird trade off and where I think this back and forth is happening - people have different mental models of the specific service they have familiarity with that they’re using to test the recommendation against and because there’s a trade off to be made, the advice can be correct in some contexts and wrong in others. If you can encode your policy and it’s evaluation generically so it flows through the stack, that’s not terrible although it becomes hard to manage certain other kinds of SLAs (eg bounding latency of your overall operation or the latency of a specific suboperation).