Designing and building a web server is something that needs the utmost care and attention, simply because an internet based business needs a server that’s reliable and is able to run 24/7 for months without requiring any servicing. This reliability is something which needs to be factored into the design from the start, and is of the utmost importance. Picking reliable components is just as important here as making sure you pick components that fit the purpose your web server is set to fulfill.
Only with a thorough analysis of what content you’ll be serving to your clients, and on what scale, you’ll be able to properly define where possible bottlenecks might arise and pick the right components for the web server without either falling short or building a system that’s overpowered. We need to make sure these bottlenecks are well understood, both in scale and frequency of occurrence and proper measures are in place to limit the effects on the performance of the server and more importantly the experience of the client.
And that’s the primary objective here; we need to make sure the website feels as responsive to the client whether there are one or one-hundred people simultaneously accessing the same content. All that counts is that the website keeps on running regardless of how many clients are being served. To accomplish that we’ll need to dig deeper than just go online, buy a couple of web servers, install the operating system, upload the content and startup the website. In the next few pages we’ll walk you through our design process for the new Hardware Analysis web server, a server designed to serve daily changing content with lots of images, movies, active forums and millions of page views every month.
Discuss This Article (28 Comments) - If you have any questions, comments or suggestions about the article and/or its contents please leave your comments here and we'll do our best to address any concerns.