zlacker

>>ZacnyL+(OP)
I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now.

It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

>>lamont+yx
I am not disagreeing with you but self-ddos is not entirely uncommon. When I worked at Amazon this would happen a few times a year. Not on the main amazon.com website but on supporting services often initiated by but not limited to kindle devices. Having something like this slip through the cracks of even experienced engineers isn't uncommon.

>>avl999+PC
But in such cases surely there's some kind of rate limiter in place?

I mean, if I'm reading that screenshot correctly this is 700+ requests a minute.

I've tripped the rate limiter with less on other sites.

>>Tade0+zF
> But in such cases surely there's some kind of rate limiter in place?

Not really, our team maintained a reverse-proxy that fronted all requests that came into amazon. And whenever we would have a self-ddos event, we'd get a request from the backend team whose service was getting self-ddos'd to shed traffic before it reached their service hosts to prevent it from browning out. In many case ddos's were coming from kindle devices which were not even easy to update so deploying a "fix" wasn't even always an option.