4 ms·
They said the system could be brought down by a RPI over DSL. My guess is that the Auth system, which became the bottleneck, authenticated everywhere at once,
by doctor_eval 3y ago
They said the system could be brought down by a RPI over DSL.
My guess is that the Auth system, which became the bottleneck, authenticated everywhere at once, which would be super slow.
Not sure what lambda had to do with this. The whole SAP thing reads like a legacy nightmare.
- teaearlgraycold 3y agoI don’t think lambda is the problem. But my guess is that using a highly scalable system that forces you to make convenience tradeoffs for that scale isn’t the best solution here. A monolithic app could handle the scale required with better devex. But I also don’t know much at all about what’s going on in that system. If the serverless tradeoffs has no real downsides for their specific use cases then all I said is moot.
- doctor_eval 3y agoYeah - I’m not personally a fan of the specific tech discussed in the article - 100 proxy requests/second could be handled by a RPi, but I suspect it was more complex than a simple proxy - but it was pretty clear that this wasn’t really the issue. The point was that the launch was predictably going to fail, it was predicted, and then it failed. And this was due to the kind of arrogant, disconnected management decisions that are sadly very familiar to many of us here at HN.