64
Fediverse sustainability
(lemmy.ml)
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
Though I was technically naive about how the fediverse could work, I was generally curious … but when I found out it’s distributed data synchronisation it was one of those moments in tech when you realise something isn’t that fancy and is done essentially the way most people would do it if they had to design it.
My presumption was that there was some robust but efficient network of servers that aided cache and data retrieval.
As you say, data synch seems to put a decent load in all servers which grows as the network does. Seems like a problem that’s been kicked down the road. As you say.
Well... KISS is a good concept for a reason. There's on paper no reason - at least before running into actual issues - to find something fancier than just replicating updates across known other network members.
Oh I know. But by 2022 the Fedi had been running for years so I’d figured something fancy had at least become necessary by that point. How much of a problem it is I don’t know but I’ve definitely heard that the load of pushing out all the sync has been significant for some servers, lemmy instances included during the migration. And then there’s the storage costs, where that’s probably a much smaller problem but might come up at some point not far down the line??