this post was submitted on 03 Jul 2023
59 points (96.8% liked)

Technology

59402 readers
3950 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Instead of one-to-one connection it implements one-to-many. Theoretically it can significantly reduce costs of self-hosted instances, increasing speed and reliability.

you are viewing a single comment's thread
view the rest of the comments
[–] qnick@lemmy.world 2 points 1 year ago

IP multicasting works when many clients request the same data at the same time, it makes sense only for realtile streams, and you need to implement caching by yourself.

In NDN caching is already included in the protocol and implemented in the forwarding daemon. It works similar to CDN. If all lemmy instances were connected to one NDN, the cache data would be spread across the entire network. So even when lemmy.world is offline, you'd be able to read it from the nearest (by ping) lemmy instance.

I stated that getting rid of IP is the goal of NDN, but it obviously cannot happen right away, because lemmy instances currently don't have any direct connection to each other. But it will eventually happen, so we better get prepared.