Building a web farm for few thousands sites

I received some nice comments on my next big project.

Thanks everybody. I think the last comment from Jeff inspire me !

Well if anybody has some thoughts about this share it.

That is the great thing about this setup. There really isnt an infrastructure nightmare. It is one web application running off several servers in a web farm. All of the "distinct" site information is data driven.

In fact the new application we are building is completely themable (different types of navigation) and completely skinnable (different color scheme's on existing themes)

There is obviously a backend administration tool that allows our customers to change their current theme, and or any information on their site.


We use F5 BigIp network load balancers and several windows 2003 servers. It is still under development so I cannot specify exactly how many servers will be used, but we plan to put 2,400 websites into production using only one code base and one application directory spread across multiple servers in a web farm.

Basically you can use DNS to just point hostnames to 1 single ip that is actually a virtual ip for all of the web farm.

We have used this same setup in an ASP legacy environment and it worked great. We hosted about 450 seperate sites on 2 web servers operating in a server farm.