3 ms·
The vast majority of WordPress-powered sites have no personalised content: the only authenticated users are 1-2 administrators, and 1+ people who add/edit conte
by rahimnathwani 8y ago
The vast majority of WordPress-powered sites have no personalised content: the only authenticated users are 1-2 administrators, and 1+ people who add/edit content.
For this use-case, it's hard to beat WordPress for features and ease-of-use, especially when you consider the ecosystem of plugins that can add commonly-needed functionality. Sure, you could roll-your-own, and then add some code to generate a sitemap.xml etc., but there's no need.
Sure, it doesn't scale without adding caching, but it's trivial to add caching with either a plugin, or by putting varnish or similar in front on the same machine, or using a CDN.
Sure, if you have dynamic or personalised content, you'll need to cache further down the stack (e.g. at the database level), and that's less efficient (because you're probably running multiple php files to generate a single HTTP response), but that's not the usual situation.