On one hand, I agree. For example, by late 2003 I was already working with PHP codebases that had adopted a roughly MVC paradigm -- routes mapped to controller objects and methods, active-record like database abstractions, and templates separated from anything but display logic -- and had an interesting optimization and caching setup. This all seemed broadly known as a good way to do things by 2005-ish.

But on the other hand: I'm not convinced this is the beginning and end of architecture considerations. We've still only been writing web apps for a bit over two decades, it's possible we still have some things to learn about how to organize them and get them to perform well. In particular, problems of scale circa 2005 aren't really the same as current problems of scale. There are just More Users on the web doing more things and we're tracking more data. We have different tools for managing all this. We're still figuring out if we like those tools.

And on top of that, we seem to be in the middle of an SPA/browser-as-VM kick that I suspect is going to look at least a little overdone and ill-considered in another five years or so.