My compnay has devloped knowledge management/publishing software which we intend to deliver to clients using an ASP model over the web. I need some assistance in designing a network that will scale well as my company grows and adds multiple clientseach using the software to run seperate web sites.
Here are some details concerning my inititial thoughts:
1. The servers need to be Windows 2000 and SQL 2000 to support the software
2. I plan to co-locate my servers at a major provider in the NY/NJ area (any suggestions for a good provider is a bonus).
3. As I have never worked with one of these large providers before I am unsure as to what they provide, other than the fast connection and an empty cage. For instance do I need a router/switch or will that be provided (typically)
4. My thinking regarding the architecture of the network is that I need a router/switch leading to a web server leading to a DNS server leading to an application server (which will execute the VB components that comprise the software) leading to a SQL server. Do I need to place hubs/routers/switches anywhere else along this chain? To save money which of these services can/should I combine on a single box?
5. If the above architecture makes sense how do I go about adding multiple clients each with their own site that maps to their own IP and domain name? Is this what the DNS servers do? or does the intitial switch dertimine the proper routing.
I have read through white papers on the Microsoft site regarding this type of architecture, but they left out many of the details. It’s the details that have me hung up.
Is/are there any documentation/books out there that would take you through such networking step-by-step? Most of the infrastructure info I am finding is relevant to office LANs, but not web-based networking.