Why to adopt "WWWn" terminology?
First of all, I must have to say thanks to my colleague Mr. Ram Nath Rao, who helped me lot to make the article concise.
We all are familiar with 'www' stands for World Wide Web, where requests are handled by a particular or dedicated server. Now, consider a scenario where a large amount of requests is to be served by the same server then there is density of traffic is high and performance is slow because delay time is increased or in other words waiting time of a particular request to start service is up.
To overcome the above scenario the "wwwn" comes into context. In this, same application is replicated on more than one servers to handle large amount of request. These servers are grouped into network,known as "Web Farm", usually put on same location. Server Farm steamlines internal processes by distributing the workload, which is known as Load Balancing, between individual servers.
With the help of above, more number of requests can be handled in less time as it reduces delay time for a particular request and the result is performance improved.
WWWn - In this n stands for any natural number i.e. 1,2,3...
Examples : www1,www2,www3
In above, 1,2,3 is nothing but are the prefixes using with 'www', representing different servers, by which request is handled, other than the one that serves the typical "WWW" address