Discussion Locked

Building a network to support an ASP

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

5 replies

by barry hensley

There is a basic model that works well for configuring application services to be delivered via the ASP model.

ASPs offer many different programs. You can outsource all of the equipment, maintenance, etc. to the ASP or, you can just buy bandwidth and a cage, populating the cage with all your own gear. It really gets down to your expertise, availability, and costs.

This question should really be answered by 2 documents.

1. A network design showing the quantity, placement, and configuration of routers, switches, fail-over devices, firewalls, etc.

2. An application architecture document that shows the performance, load, storage, redundancy, and scalability requirements of the application.

I can help to prepare both of thesedocuments but it is going to take a lot more work than what can be done here. Wait for a few more answers. If you don't get anything substantial, send me an email at bhensley@intellify.com and I'll help out.

by mckaytech

It's not possible to give a complete answer in the 1930 characters allotted but I can fill in a few of the details.
A co-location provider will usually provide rack space, clean power and a fast network connection. Everything else is negotiable and they can provide the server hardware also, if you wish. Their router is the gateway to your network so generally you would not need to supply a router and usually they will provide DNS services as well (sometimes they insist on providing that piece).
There are a couple of philosophies on server allocation but the choice should be guided by performance and eliminating as many single points of failure as possible. You could use three separate servers but you would then have three points of failure that could disrupt your operations. An alternate might be to have two load-balanced servers that provide all three services (Web, application, SQL) or perhaps two front-end servers providing the front end (Web and application) and a clusteredpair of servers providing the backend (SQL).
As far as the multiple clients question, you would set up multiple virtual hosts on your Web server, then use DNS to map the domain name to the correct virtual host.

paul

This discussion is closed to new replies.