Why DHT network, Pros and cons
1. Do not have to rely on torrent index sites. If the torrent sites are temporarily unavailable or even disappear, the torrents are still active and available on DHT network.
2. If your address is anonymous (VPN-based, proxy-based), you will not be penalized to access the network via standard or extended Bit Torrent protocol. Membership sites can limit and ban trouble peers. Peers that has a very imbalanced ratio of seeding vs. leeching.
3. Full access to DHT without having to logging in.
4. Torrent sites may not have the particular torrent or category you are looking for.
5. The number of seeders and leechers reported by the torrent sites may not be up to date or even valid depending upon the current DHT network traffic.
6. Torrent sites show the most popular torrents and trends in a certain time frame but these may not be what you are interested in.
7. With extended BitTorrent protocol, DHT enables any participating peer without having to download or share anything to look at the torrent queue of a specific peer (IP address).
8. With DHT, the most popular trends can be established quickly by looking for the hash that has the most number of unique peers and leechers. Because of this feature it is possible to monitor the sharing activities of a specific peer.
Multiple dedicated Linux servers for
distributed website management.

Since you own the server, you can tailor not only the operating system functions but also the server hardware configuration to support specific software packages to match your company business image and requirements. The growth path is already built into your dedicated network. You can add larger and faster hard disks to support more contents and additional websites. Larger databases can be handled by additional dedicated servers, and at the same time make all of your web sites more responsive.

The above scenario illustrates a dedicated web server connected to a local backend database and email server so that the work load is properly distributed to support high-traffic websites. Requests from visitors which require database operations are processed by a dedicated database server. Automatic email responses and payment notifications are processed by a separate email server. For additional security, both the database and email server are not accessible or visible to Internet visitors. Linux is well-known for its scalability and security model to build professional image and growth.

Multiple dedicated Linux servers for
the deployment of Intranet applications.

The above scenario illustrates a typical Intranet configuration to support the development of large commercial websites. A development web server communicates with other servers and test client computers within a local network connected through a hardware switch.

The test client computers can be on any platform such as Windows Vista, XP, and Linux desktop. Typical additional servers perform functions for SQL databases, file archiving and application support, automatic backup and replication, email spam management, etc. Contents can be conveniently developed and tested from a popular Windows platform using off-the-shelf tools.

The entire local Intranet is not visible from the Internet. The development web server can synchronize its data with the production web server via traditional FTP or SSH. The data transfer uses a gateway server which enforces all security rules and firewall policies to protect the local Intranet network. The gateway server provides Internet access to all computers in the local network by sharing a single broadband connection.

The production web server is simply a mirror image of the development web server. Backing up the contents of the production web server is no longer a critical priority or even needed.