1. Single Thread Web server
In this way, the Web server processes one request at a time, and then reads and processes the next request at the end. During the processing of a request, all other requests are ignored, so there will be serious mandatory problems in scenarios where there are more concurrent requests.
2, multi-process/multi-threaded Web server
In this architectural approach, the Web server generates multiple processes or threads that process multiple user requests in parallel, and processes or threads can be generated on demand or in advance. There are Web server applications that generate a single process or thread for each user request, but when the number of concurrent requests reaches tens of thousands, multiple concurrently running processes or threads consume a large amount of system resources.
3.i/o multiplexing Web server
In order to be able to support more concurrent user requests, more and more Web servers are using multiple reuse architectures-synchronous monitoring of the active state of all connection requests, a series of specific actions for a connection when the state of a link changes (such as the data is ready or an error occurs), and after the operation is complete, This connection will be reset back to the transient stable state and returned to the list of open connections until the next status change. Because of its multiplexing nature, processes or threads are not occupied by idle connections, and thus provide an efficient mode of operation.
4. Multiplexing multi-threaded Web server
A Web server architecture that combines multi-process and multiplexed functionality to avoid having a process serve too many user requests and take advantage of the computing power provided by multi-CPU hosts. The Web server itself does not handle any dynamic content, how does it respond to a client's dynamic content request? The additional process is invoked through some protocol to run the dynamic page, and the result is returned to the Web server later, in response to the client.
How the Web server handles connection request schema
