@reiver …and it's not just the sheer amount of storage; prudent expiration and cleanup (e.g., #Enigmatick clears cache data each night that's greater than 30 days old) helps to manage that. It's the application load of pulling up the same records tens of thousands of times within a few seconds when new content is created (i.e., the fan-out of initial delivery and the resulting requests back for content).

I use Varnish and that helps a lot with the latter case. But a #FediCDN could be built on Varnish (like Fastly is) and provide decentralization in that service.

3/

[Fediverse CDN]

Once you have Fediverse Caching servers — you have the basis to create a Fediverse content-distribution-network (CDN).

A (Fediverse-native) Fediverse content-distribution-network (CDN) could bring a new level of robustness and scalability to the Fediverse — while still maintaining the properties of decentralization, federation, and localization.

#CDN #ContentDeliveryNetwork #ContentDistributionNetwork #FediCDN #FediDev #FediDevs #Fediverse

2/

[Fediverse CDN]

One way to increase the robustness of the Fediverse is — to introduce the concept of a Fediverse Caching server.

It (the Fediverse Cachine server) caches stuff from the Fediverse rather than the regular Fediverse servers (that house local users and local content).

...

#CDN #ContentDeliveryNetwork #ContentDistributionNetwork #FediCDN #FediDev #FediDevs #Fediverse