| Highwinds Software Product Documentation: Typhoon, Twister, Tornado, Hurricane, and Cyclone | ||
|---|---|---|
| <<< Previous | Next >>> | |
When building and configuring a Usenet architecture a difference often exists between making it work and making it work right. The difference is subtle, in most cases, until optimizations are made. Only then will your bandwidth bill be cut in half, or your servers be twice as available or some other proverbial light bulb will light up and make you gasp What was I thinking?. Then again, maybe you're just interested in setting up a full and robust Usenet architecture - either way, we hope this helps.
The goal of this technical article is to outline some essential Usenet article architectural and routing concepts that allow you to:
Get the most reliability from your network (Directly translates to "sleep at night and on the weekends").
Minimize resource consumption and maximize efficiency
Allow you to scale with the ever-growing size of a Usenet feed.
If you doubt that Usenet is still growing after 20+ years, see the graph below:
| <<< Previous | Home | Next >>> |
| Configuration | Up | Split Feeding |