The document discusses web servers such as IIS, Apache, and Nginx, outlining their functionality in processing HTTP requests. It highlights the history of web servers, different types including dedicated and cloud servers, and compares performance metrics between Apache and Nginx. Additionally, it addresses the strengths of both Apache and Nginx, as well as the possibility of using them together for enhanced setups.

1. WEB SERVERS(IIS, APACHE,
NGINX)

2. WEB SERVER
• Processes requests via HTTP
• Every Web server has an IP address and possibly a domain
name.
1. URL http://www.webopedia.com/index.html
2. sends a request to webopedia.com
3. sends index.html to your browser.
1

3. STRUCTURE OF WEB SERVER
• 1) Client sends request to server.
• 2) Server accepts the request and then process it.
• 3) Server sends back the request to client.
2

4. HISTORY
• 1989
• CERN httpd
• Sir Tim Berners-Lee
3

5. TYPES OF WEB SERVERS
• Dedicated Server:
physical server
purchased or rented for your own
business needs
For large businesses
high levels of data security
running 24*7*365
• Cloud Server:
virtual server
less costs
for small and mid-sized businesses
Web Servers
Cloud Servers
Dedicated
Servers
4

6. HANDLE REQUESTS
1. append the given path to the path of root directory
• Root directory in configs
• Https://arastu.ir/a/b/c.pdf
/home/arastu/www/arastu.ir/a/b/c.pdf
2. Create Response
• Based on configs
• Create response dynamically with server side programming languages
• Return static file
• Error
5

7. WEB SERVERS
•IIS
•Apache
•Nginx
6

8. IIS
• Components:
• HTTP .sys
• Worker processes (w3wp.exe)
• ISAPI
• InetInfo.exe
• Application pools
7

9. 8

10. Apache server
Child Process
Shared Memory
Child Process
Database,
HTML
projects
APACHE
9

11. 1
0

12. APACHE VS NGINX
• Ubuntu 18.04
• Apache 2.4.29 (mpm_event)
• Nginx 1.14.0
• Default settings
• 1GB ram
• 1 CPU
1
1

13. APACHE VS NGINX(request handling)
• Ubuntu 18.04
• Apache 2.4.29 (mpm_event)
• Nginx 1.14.0
• Default settings
• 1GB ram
• 1 CPU
APACHE NGINX
670.53 rps 660.15 rps
1
2

14. 1
3

15. 1
4

16. • Apache averaged a CPU usage 20% and 18MB RAM
• NGINX averaged a CPU usage 12% and 8MB RAM
if your biggest concern is performance & efficient use of your
resources you should consider using Nginx.
1
5

17. Popularity
1
6

18. Popularity
• According to the 2018 August Web Server Survey conducted by
netcraft.com, these are the stats for active sites:
• Apache 38.68% (-0.62 from previous month)
• nginx 22.67% (+0.11 from previous month)
1
7

19. APACHE STRENGTHS
• Runs PHP applications (like Wordpress) without external
software, just install mod_php if it isn't already part of the
default install for your distribution.
• Works great in a shared environment (like a hosting provider)
because it supports directory-based configuration with
.htaccess files.
1
8

20. NGINX STRENGTHS
• Serves static assets very efficiently thanks to its event-driven
approach to handling requests.
• Is a great proxy & cache layer for the same reason.
1
9

21. COMBINATION OF APACHE AND NGINX
Apache & Nginx can be used together, with Nginx proxying non-
static asset request to Apache. This can add significant
complexity to your setup, but it's something to consider if you
want to use features from both.
2
0

22. APACHE VS IIS
2
1

23. LOAD BALANCING
2
2

24. PROXY
2
3