Because it's the company with a thousand developers (Cloudflare) who's dealing with this.

I think the self congratulatory tone is just them saying if you design things simply you can do a lot (load) with a lot less (people/complexity) and still have an app that’s resilient (ignore minor ddos issues).

It’s encouraging or reminding people that this style of architecture, which was once prevalent, is still an option and is still rather legit.

Or, that’s how I read it however I also am biased as I prefer this method of development too. I think what’s missing in the article is, who are they and who is the audience. As in, some acknowledge that most things are not ever going to see mass scale usage and don’t need to be developed to the specs of a faang

Except that it wasn't their architecture which allowed them to weather this storm: it's Cloudflare's. And the storm is a whopping 1.85 requests per second, all coming from Europe which means this isn't even a DDoS to begin with.

But they didn't active the "Under Attack" mode in Cloudflare, so surely they must be doing it all by themselves.

sarcasm is hard to read in text; missing /s

Probably mincing words but I guess I consider cloudfare part of the architecture and not part of their infrastructure and it seems like you’re conflating the two?

I do get that the volume of data and requests they are handling hardly constitutes the claim of ddos.

Exactly, the same way that "the cloud" is just someone else computer and responsibility.

> But typically this take would be assumed by a FAANG company to require over a thousand developers?

Using a CDN has been common practice for many years at companies big and small. Many big CDNs even have free tiers.

> Like how can claim it’s self congratulatory when huge companies regularly can’t do this?

You don’t need a FAANG company with thousands of developers to use a CDN. You can sign up for Cloudflare today and have your files distributed by CDN with some simple changes. You could have it done by end of day.