Not aussieguy, but cache everything on the network level. If you need anything dynamic, do it SPA style and bypass the WordPress backend. There's no getting ar

Not aussieguy, but cache everything on the network level. If you need anything dynamic, do it SPA style and bypass the WordPress backend. There's no getting around the 50-200 request/sec barrier of the codebase. The most popular sites use it as a fancy static site generator. Write your dynamic stuff in React or Vue (something client side). Then point it at a custom backend built to handle the load. For comments and the like, maybe mongo or elastic with Go/Java. I've only seen a couple sites popular enough to do this. A danger with WordPress is attackers finding a stray dynamic endpoint (not cached) and taking site down by curling or F5. Unless you have a super beefy server, it's possible to kill a site spamming F5 if you find an action not cached. This is a technical problem for all WordPress sites but only a practical one for sites large enough to be a target. Some sites the use sitemap functionality to pregenerate all pages as HTML and serve that. It's the only way to be truly secure with WordPress