News for hackers. Stuff that matters.
Re:How to Build Software Like an SRE by quadrifoliate on Monday October 17, 2022 @08:19AM (#33232514)
> TCP retries won't help if your backend is restarting, if failover switching is happening, if your overloaded cluster has just been scaled up to add nodes, etc.

Yeah, this is where the nuance begins.

You are correct that TCP is not always sufficient. Perhaps where we differ is that in my experience, it still helps for this to be a feature of the framework that the applications are running on (e.g. a retry budget in the service mesh, or a load balancer) rather than scattered around in the application itself. At some point it becomes a word game – you could say that the service mesh is also kind of an "application" itself.

Otherwise, you will find that N developers who are tasked with figuring out something like this will scatter N different version of your exponential randomized delay policy all across your codebase. It is always possible to avoid this with enough code review discipline, but once the trend starts, it's much harder to say "No, you need to fix this the right way".

Re:How to Build Software Like an SRE by sarchertech on Monday October 17, 2022 @08:40AM (#33232681)
I’ve seen this exact problem many times. Counting TCP, the current system I’m working has 5 different layers of retries.

TCP, the service mesh, the company wide http client, application retries, and a database backed queueing library that everyone uses.

Imagine what happens when a service is flaky and each one of those layers retries 3-5 times.

Re:How to Build Software Like an SRE by Jupe on Monday October 17, 2022 @04:53PM (#33239390)
Yep. And then the user says.. "Oh, that didn't work - I'll just try again... and again..."