3 ms·
To be honest, if you dynamically generate a site and include the relevant headers, a web cache in front of the site will do all the "compilation" without any of
by ealexhudson 7y ago
To be honest, if you dynamically generate a site and include the relevant headers, a web cache in front of the site will do all the "compilation" without any of the headache of a specific ahead-of-time process.
If you get a really large site (= in terms of pages), it's often easier to invalidate an entire cache and allow it to rebuild lazily than go through and linearly reprocess every page, and you don't get any examples of pages having both "old" and "new" content as you browse the site while republishing is taking place (although you can also accomplish this with content-switching once the full rebuild was done).
- baybal2 7y agoPlain database read requests for items in an index aren't loading the CPU anywhere near as just any collation tasks in a scripting language. Having such things being AJAX loadable is still the best option.
- zozbot234 7y agoWikipedia does this. Logged-out readers get cached versions of the Wikipedia page (though they can use a manual "purge" action in order to trigger an update when needed), logged-in users get a SSR version rendered by PHP starting from replica databases. Edits go to the master/source-of-truth DB.