News for hackers. Stuff that matters.
Re:Lessons learned writing highly available code by mjb on Friday October 02, 2015 @06:01PM (#10321616)
Absolutely. I made some graphs of different kinds of jitter approaches at http://www.awsarchitectureblog.com/2015/03/backoff.html. Simply backing off with delay does very little to spread out spikes of work, and can lead to longer MTTRs if the cause of the issue was overload.
Re:Lessons learned writing highly available code by sgk284 on Saturday October 03, 2015 @05:41AM (#10323261)
Would it be possible for the server to simply return a queue position to the contending clients? For instance, "There are 37 clients ahead of you. Try again in 37ms." (assuming each write is averaging 1ms)

I suspect if the client and server worked together in this fashion you could get much closer to the linear completion time seen with no backoff and also closer to linear work (since each client would try exactly twice in an ideal world where the server accurately predicted when it should try again).

Re:Lessons learned writing highly available code by cpeterso on Friday October 02, 2015 @10:56PM (#10322422)
Sorry. I accidentally down voted your comment when trying to up vote it on my phone! The article was very interesting.