bittorrent-dht VS torrent-paradise

I'm not talking about the consensus protocol of the blockchain itself, but of the p2p algorithms underlying it, e.g. using Kademlia for service discovery and message routing. I'm asking why a distributed system would choose something like Consul (which uses Raft, and requires a coordinator node) instead of running a decentralized protocol like Kademlia (which has no coordinator nodes) within their distributed single-tenant environment.

I did a bit more research last night, and discovered that Bitfinex actually does something like this internally (anyone know if this is up to date?) [0] — they built a service discovery mesh by storing arbitrary data on a DHT implementing BEP44 (using webtorrent/bittorrent-dht [1]).

This seems pretty cool to me, and IMO any modern distributed system should consider running decentralized protocols to benefit from their robustness properties. Deploying a node to a decentralized protocol requires no coordination or orchestration, aside from it simply joining the network. Scaling a service is as simple as joining a node to the network and announcing its availability of an implementation of that service.

At first glance, this looks like a competitive advantage, because it decouples the operational and maintenance costs of the network from the size of the network.

So I'm wondering if there is a consistent tradeoff in exchange for this robustness — are decentralized applications more complex to implement but simpler to operate? Is latency of decentralized protocols (e.g. average number of hops to lookup item in a DHT) untenably higher than that of distributed protocols (e.g. one hop once to get instructions from coordinator, then one hop to lookup item in distributed KV)? Does a central coordinator eliminate some kind of principle agent problem, resulting in e.g. a more balanced usage of the hashing keyspace?

Decentralization emerged because distributed solutions fail in untrusted environments — but this doesn't mean that decentralized solutions fail in trusted environments. So why not consider more decentralized protocols to scale internal systems?

[0] https://github.com/bitfinexcom/grenache

[1] https://github.com/webtorrent/bittorrent-dht

Yes the database is fixed. I would like to make it updateable using web2web or mutable torrents (BEP44) which the WebTorrent DHT supports.

There’s also this which has since gone down but remains up on IPFS and its index hasn’t updated since January…

https://github.com/urbanguacamole/torrent-paradise

https://cloudflare-ipfs.com/ipfs/QmQjsKamNFZRvCMXDvZXQmRYjsm...

For what its worth the source code is still up if anyone wants to create a new site using the code https://github.com/urbanguacamole/torrent-paradise

For years after we missed torrentz.eu, torrent-paradise.ml was my best torrent search engine. Clean, powerful and uptodate. Sadly it is disabpear in mid january 2022 for reason that I don't know. I'm wondering if there is any clone/alternatives, as the source code is available here

The code and instructions are still at https://github.com/urbanguacamole/torrent-paradise

related: https://torrent-paradise.ml/ Also based on IPFS with this HTTP gateway. I find a lot of torrents in there.

Torrent Paradise

I'm only on private, invite only torrent sites right now, so I'm not much help with regard to public trackers. I do have https://torrent-paradise.ml/ bookmarked which seems to be an aggregator of many other trackers.

It would be great to add this very interesting and valuable torrent site in already awesome provider packages for Syncler. Here is the link for the site https://torrent-paradise.ml/