187
What are some downsides of software being federated? (lemm.ee)
submitted 3 years ago by to c/asklemmy@lemmy.ml
122 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 83 points 3 years ago (3 children)

The overhead of duplicated data across the network. Not reposts on different instances, but the software itself on those different instances needing to cache/store this one single post for their users locally

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 38 points 3 years ago (2 children)

    Don’t large services have many duplicates/caches spread across the globe to balance load and reduce latency? Couldn’t this be seen as a positive? It could also be seen as a redundancy layer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 22 points 3 years ago

    Yes. It's very common to cache content closer to the user, otherwise the site would be slow. Some services like Netflix and Facebook even provide custom caching servers to internet providers to install in their data centers. These are called Netflix Open Connect and Facebook Network Appliance respectively. They significantly reduces costs for the ISP, as Netflix and Facebook are generally two of the heaviest users of bandwidth on an ISP's network, and traffic entirely within their own network is effectively "free" for them.

    This is a good part of federation IMO - if users join an instance physically close to them, their experience is going to be nice and fast, since everything is cached on their instance. It's also pretty easy to spin up a new Lemmy instance in your country if one doesn't exist yet.

  • permalink
  • fedilink
  • source
  • parent