Welcome
Topic #1.1.1.1.1.1.
Up To: The Hub
   Read: Process Controller  
   Read: Single Server  
   >>Multiple Servers  
   Read: Kiosk Design  
   Read: Modular Apps  

to to to to to to Multiple Servers

Browsing >>Multiple Servers: Design for a high-traffic web application

High traffic design
Web server cluster with separate database server

Description
Multiple surfers, using web browsers, connect to a machine running NT, a web server, a WebHub runner, The Hub, and multiple instances of the application server (EXE). There can be one or more such web server machines. The database is kept on a separate machine.

Benefits to this Design
This design is able to support more traffic than the low-to-medium traffic example because:

  • The database is isolated on a separate server. The database processing has the resources of a dedicated machine, and the CPU on the WebHub machine is able to work on surfer B in a second EXE while surfer A is waiting for the database answer to return to the first EXE. In this situation, even a single-processor WebHub machine will be able to serve many surfers in parallel.

  • There are additional web server/WebHub machines in what's known as a "server farm" or "cluster." More physical machines allow you to serve even more surfers, up to the limits of your database server. Typically there is one "main web address" that surfers come in to, and they are then routed either by hardware or software to one of the machines in the cluster.

Running: WebHub-v3.270 compiled with d25_win32 on Microsoft-IIS/10.0,
Tue, 21 Nov 2017 00:33:35 UTC
Session 1723384735, 0 pages sent to CCBot/2.0 (http://commoncrawl.org/faq/) at 54.81.139.56;
Time to produce this page: 15msec.