3 ms·
> Generating static content and saving to a CDN is just a really inefficient way of caching dynamic content. Disagree; updating your content when (and only whe
by lmm 6y ago
> Generating static content and saving to a CDN is just a really inefficient way of caching dynamic content.
Disagree; updating your content when (and only when) it changes sounds a lot more efficient than dynamically generating whenever it's requested and then putting a cache in front of that.
- altdatathrow 6y agoThat's called cache warming and high-volume sites have been utilizing that upon deploy for decades.
- lmm 6y agoCache warming is an overcomplicated way to achieve most of the same thing. You already know exactly what's changed; why would you throw that information away and then attempt to regenerate it, instead of just using it directly?
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- TuringTest 6y agoHow well does cache warming support users editing the content directly on the database and control-versioning it? Witch static webpage generators, your non-technical editors get all the benefits from editing flat-text files with markdown and git, instead of relying on a sys-admin to watch the state of the database for them.
- deleted 6y ago[deleted]