Yea, ideally all these things should have pretty aggressive caching around them, I suppose a CDN could help lower their resource costs even more… but I think the vast majority of work will be retrieving dynamic data like posts and comments.
Yeah. Serving static assets is not a big deal with a decent web server. You can get servers with unmetered transfer and the CPU and memory for static resources is tiny. Main reason to use a CDN is latency.
IF the static assets like images and video are being served by the application from other network sources or out of a database then a caching CDN would be a big win for sure.
What types of read calls would you put behind a CDN in lemmy?
Probably everything that’s static like images, JavaScript, css
Just have a cache invalidation strategy.
Yea, ideally all these things should have pretty aggressive caching around them, I suppose a CDN could help lower their resource costs even more… but I think the vast majority of work will be retrieving dynamic data like posts and comments.
Yeah. Serving static assets is not a big deal with a decent web server. You can get servers with unmetered transfer and the CPU and memory for static resources is tiny. Main reason to use a CDN is latency.
IF the static assets like images and video are being served by the application from other network sources or out of a database then a caching CDN would be a big win for sure.