For a very small instance with only a couple of concurrent users a CDN might not make much difference. But if you take a look at your web server logs you’ll quickly notice that every post / like / vote triggers a storm of requests from other instances to yours, looking up lots of different […]
For a very small instance with only a couple of concurrent users a CDN might not make much difference. But if you take a look at your web server logs you’ll quickly notice that every post / like / vote triggers a storm of requests from other instances to yours, looking up lots of different things. It’s easy to imagine how quickly this would overwhelm an instance once it gets even a little busy.
One of the first web performance tools people reach for is to use a CDN, like Cloudflare. But how much difference will it make? In this video I show you my web server logs before and after and compare them.
Flippin' eck. Seeing a familiar Lemmy post on there, clicking it and seeing the whole thing render instantly was a bit of a shock after getting used to Lemmy's more pedestrian loading of stuff.
Using a CDN does not come without downsides, though. Cloudflare itself is becoming another "too big to fail" entity of a system that is not supposed to depend on the resilience/capacity/budget of any single actor.
Personally, I'd rather see a tiered architecture for data, where servers are only responsible for guaranteeing the data from actors on their own servers, but everything else stored in a distributed, append-only stream of data. This would make a lot cheaper to run individual instances and would allow clients to obtain the data from multiple sources.
Oh I love the topics list. It already helped me discover a new community. I assume right now it's curated by someone, would be cool if there was a way for communities to just apply tags to themselves. They could even be turned into hashtags, whenever someone posts to that community, as a kind of link to Mastodon.