4 ms·
I agree with you in general, but in this particular case they knowingly deployed thread-unsafe code in production while increasing the threaded concurrency. Tha
by petters 6y ago
I agree with you in general, but in this particular case they knowingly deployed thread-unsafe code in production while increasing the threaded concurrency. That should have broken internal development rules.
- eli 6y agoNow imagine what happens behind the scenes at other service providers. I’d bet the ones that have policies that bury the details of incidents, on average, have worse problems.
- simonw 6y agoIt sounds to me like they created new internal development rules as a result, which is a smart response to the issue.
- yuliyp 6y agoYes. Writing code with bugs breaks internal development rules. The issue wasn't thread-unsafe code. It was confusion about object lifecycle. An env object was assumed to no longer be used by the web framework after a request terminated, while in reality it was recycled for future requests as a performance optimization.