![\"apachevsnginx\"](\"https:\/\/www.wpoven.com\/blog\/wp-content\/uploads\/2014\/09\/apachevsnginx.png\" "\\"\\"")
<\/a><\/p>\n\nWhat is Nginx and Apache<\/strong><\/em><\/span><\/h2>\n <\/p>\n
Nginx (Pronounced Engine-x) and Apache, both are open source web servers.<\/p>\n
The Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem<\/a>\u00a0and some performance and scalability issues associated with Apache.<\/p>\n<\/p>\n
How They Work<\/strong><\/em><\/span><\/h2>\n <\/p>\n
Apache<\/em><\/span><\/h3>\n\u0097Apache \u00a0handles HTTP Requests sent to it.\u00a0It creates processes and threads to handle additional connections. The administrator can configure the server to control the maximum number of allowable processes. This configuration varies depending on the available memory on the machine. Too many processes exhaust memory and can cause the machine to swap memory to disk, thus severely degrading performance. Plus, when the limit of processes is reached, Apache refuses additional connections.\u00a0Apache is comprised of Two main building Blocks with the Latter being comprised of many other little building blocks. The Building Blocks are the Apache Core and then the Apache Modules that in a sense extend the Apache core.<\/p>\n
<\/p>\n
![\"02kew01\"](\"https:\/\/www.wpoven.com\/blog\/wp-content\/uploads\/2014\/09\/02kew01.gif\" "\\"\\"")
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache.<\/em><\/h3>\n\u2014\u00a0Chris Lea on nginx and WordPress<\/strong><\/h4>\n <\/p>\n
<\/p>\n
Nginx<\/em><\/span><\/h3>\nNginx works differently from Apache, specially how it handles threads. It uses\u00a0Event-driven<\/strong>, asynchronous<\/strong>, non-blocking and single threaded<\/strong> architecture.<\/p>\n\n- Event Driven :\u00a0<\/strong>The starting and completion of events are marked by notifications, therefore the resources can be used by the other process until a process start or completion notification is received.
\n<\/span><\/li>\n- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n
- Single Threaded :\u00a0<\/strong> As the resources are not blocked therefore, multiple clients can be handled by a single worker process.<\/li>\n<\/ul>\n
The following diagram represents the Nginx architecture :<\/p>\n
<\/p>\n
![\"nginx-architecture\"](\"https:\/\/www.wpoven.com\/blog\/wp-content\/uploads\/2014\/09\/nginx-architecture.png\" "\\"\\"")
<\/a><\/p>\n<\/h2>\n<\/h2>\n<\/h2>\n<\/h2>\n
<\/p>\n
\u00a0<\/strong><\/p>\nPros and Cons<\/strong><\/em><\/span><\/h2>\nApache<\/span><\/h3>\n\u00a0Pros<\/em> :<\/strong><\/p>\n\n- Large number of Modules:\u00a0<\/strong>Apache been available since many years and \u00a0has a larger community base, therefore has lots of Open-source modules written to expand it’s functionality.<\/li>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Large number of Users :\u00a0<\/strong>Nearly 46% of all websites run on Apache.<\/li>\n<\/ul>\n
Cons<\/em> :<\/strong><\/p>\n\n- Less Secure<\/strong> than nginx.<\/span><\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
\u00a0<\/span><\/h5>\nNginx<\/span><\/h3>\nPros<\/em> :<\/strong><\/p>\n\n- Fast<\/strong> : It does not create a new process for each new request, therefore it becomes very fast.<\/span><\/li>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Easy Scalability:<\/strong>\u00a0Nginx is highly scalable, and it’s performance is not dependent on hardware.<\/li>\n<\/ul>\n\n
Cons<\/em>:<\/strong><\/p>\n\n- Does not support Operating Systems<\/strong> like OpenVMS and IBMi.<\/span><\/li>\n
- Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
<\/p>\n<\/div>\n
\u00a0Conclusion\u00a0<\/strong><\/em><\/span><\/h2>\nWith the above advantages in mind, more and more people are moving towards Nginx. Even WordPress.com was shifted over to Nginx and they have thousands of servers, serving thousands of requests per second. Also Nginx has become the number 1 web server for the top 10,000 websites on the internet (Read more<\/a>).<\/p>\n <\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
![\"apachevsnginx\"](\"https:\/\/www.wpoven.com\/blog\/wp-content\/uploads\/2014\/09\/apachevsnginx-1024x515.png\" "\\"\\"\/")
\nWhat is Nginx and Apache
\n
\nNginx (Pronounced Engine-x) and Apache, both are open source web servers.
\nThe Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem\u00a0and some performance and scalability issues associated with Apache. … <\/p>\n
<\/p>\n
How They Work<\/strong><\/em><\/span><\/h2>\n <\/p>\n
Apache<\/em><\/span><\/h3>\n\u0097Apache \u00a0handles HTTP Requests sent to it.\u00a0It creates processes and threads to handle additional connections. The administrator can configure the server to control the maximum number of allowable processes. This configuration varies depending on the available memory on the machine. Too many processes exhaust memory and can cause the machine to swap memory to disk, thus severely degrading performance. Plus, when the limit of processes is reached, Apache refuses additional connections.\u00a0Apache is comprised of Two main building Blocks with the Latter being comprised of many other little building blocks. The Building Blocks are the Apache Core and then the Apache Modules that in a sense extend the Apache core.<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache.<\/em><\/h3>\n\u2014\u00a0Chris Lea on nginx and WordPress<\/strong><\/h4>\n <\/p>\n
<\/p>\n
Nginx<\/em><\/span><\/h3>\nNginx works differently from Apache, specially how it handles threads. It uses\u00a0Event-driven<\/strong>, asynchronous<\/strong>, non-blocking and single threaded<\/strong> architecture.<\/p>\n\n- Event Driven :\u00a0<\/strong>The starting and completion of events are marked by notifications, therefore the resources can be used by the other process until a process start or completion notification is received.
\n<\/span><\/li>\n- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n
- Single Threaded :\u00a0<\/strong> As the resources are not blocked therefore, multiple clients can be handled by a single worker process.<\/li>\n<\/ul>\n
The following diagram represents the Nginx architecture :<\/p>\n
<\/p>\n
<\/a><\/p>\n<\/h2>\n<\/h2>\n<\/h2>\n<\/h2>\n
<\/p>\n
\u00a0<\/strong><\/p>\nPros and Cons<\/strong><\/em><\/span><\/h2>\nApache<\/span><\/h3>\n\u00a0Pros<\/em> :<\/strong><\/p>\n\n- Large number of Modules:\u00a0<\/strong>Apache been available since many years and \u00a0has a larger community base, therefore has lots of Open-source modules written to expand it’s functionality.<\/li>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Large number of Users :\u00a0<\/strong>Nearly 46% of all websites run on Apache.<\/li>\n<\/ul>\n
Cons<\/em> :<\/strong><\/p>\n\n- Less Secure<\/strong> than nginx.<\/span><\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
\u00a0<\/span><\/h5>\nNginx<\/span><\/h3>\nPros<\/em> :<\/strong><\/p>\n\n- Fast<\/strong> : It does not create a new process for each new request, therefore it becomes very fast.<\/span><\/li>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Easy Scalability:<\/strong>\u00a0Nginx is highly scalable, and it’s performance is not dependent on hardware.<\/li>\n<\/ul>\n\n
Cons<\/em>:<\/strong><\/p>\n\n- Does not support Operating Systems<\/strong> like OpenVMS and IBMi.<\/span><\/li>\n
- Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
<\/p>\n<\/div>\n
\u00a0Conclusion\u00a0<\/strong><\/em><\/span><\/h2>\nWith the above advantages in mind, more and more people are moving towards Nginx. Even WordPress.com was shifted over to Nginx and they have thousands of servers, serving thousands of requests per second. Also Nginx has become the number 1 web server for the top 10,000 websites on the internet (Read more<\/a>).<\/p>\n <\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
\nWhat is Nginx and Apache
\n
\nNginx (Pronounced Engine-x) and Apache, both are open source web servers.
\nThe Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem\u00a0and some performance and scalability issues associated with Apache. … <\/p>\n
\u0097Apache \u00a0handles HTTP Requests sent to it.\u00a0It creates processes and threads to handle additional connections. The administrator can configure the server to control the maximum number of allowable processes. This configuration varies depending on the available memory on the machine. Too many processes exhaust memory and can cause the machine to swap memory to disk, thus severely degrading performance. Plus, when the limit of processes is reached, Apache refuses additional connections.\u00a0Apache is comprised of Two main building Blocks with the Latter being comprised of many other little building blocks. The Building Blocks are the Apache Core and then the Apache Modules that in a sense extend the Apache core.<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache.<\/em><\/h3>\n\u2014\u00a0Chris Lea on nginx and WordPress<\/strong><\/h4>\n <\/p>\n
<\/p>\n
Nginx<\/em><\/span><\/h3>\nNginx works differently from Apache, specially how it handles threads. It uses\u00a0Event-driven<\/strong>, asynchronous<\/strong>, non-blocking and single threaded<\/strong> architecture.<\/p>\n\n- Event Driven :\u00a0<\/strong>The starting and completion of events are marked by notifications, therefore the resources can be used by the other process until a process start or completion notification is received.
\n<\/span><\/li>\n- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n
- Single Threaded :\u00a0<\/strong> As the resources are not blocked therefore, multiple clients can be handled by a single worker process.<\/li>\n<\/ul>\n
The following diagram represents the Nginx architecture :<\/p>\n
<\/p>\n
<\/a><\/p>\n<\/h2>\n<\/h2>\n<\/h2>\n<\/h2>\n
<\/p>\n
\u00a0<\/strong><\/p>\nPros and Cons<\/strong><\/em><\/span><\/h2>\nApache<\/span><\/h3>\n\u00a0Pros<\/em> :<\/strong><\/p>\n\n- Large number of Modules:\u00a0<\/strong>Apache been available since many years and \u00a0has a larger community base, therefore has lots of Open-source modules written to expand it’s functionality.<\/li>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Large number of Users :\u00a0<\/strong>Nearly 46% of all websites run on Apache.<\/li>\n<\/ul>\n
Cons<\/em> :<\/strong><\/p>\n\n- Less Secure<\/strong> than nginx.<\/span><\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
\u00a0<\/span><\/h5>\nNginx<\/span><\/h3>\nPros<\/em> :<\/strong><\/p>\n\n- Fast<\/strong> : It does not create a new process for each new request, therefore it becomes very fast.<\/span><\/li>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Easy Scalability:<\/strong>\u00a0Nginx is highly scalable, and it’s performance is not dependent on hardware.<\/li>\n<\/ul>\n\n
Cons<\/em>:<\/strong><\/p>\n\n- Does not support Operating Systems<\/strong> like OpenVMS and IBMi.<\/span><\/li>\n
- Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
<\/p>\n<\/div>\n
\u00a0Conclusion\u00a0<\/strong><\/em><\/span><\/h2>\nWith the above advantages in mind, more and more people are moving towards Nginx. Even WordPress.com was shifted over to Nginx and they have thousands of servers, serving thousands of requests per second. Also Nginx has become the number 1 web server for the top 10,000 websites on the internet (Read more<\/a>).<\/p>\n <\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
\nWhat is Nginx and Apache
\n
\nNginx (Pronounced Engine-x) and Apache, both are open source web servers.
\nThe Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem\u00a0and some performance and scalability issues associated with Apache. … <\/p>\n
<\/p>\n
<\/p>\n
Nginx<\/em><\/span><\/h3>\nNginx works differently from Apache, specially how it handles threads. It uses\u00a0Event-driven<\/strong>, asynchronous<\/strong>, non-blocking and single threaded<\/strong> architecture.<\/p>\n\n- Event Driven :\u00a0<\/strong>The starting and completion of events are marked by notifications, therefore the resources can be used by the other process until a process start or completion notification is received.
\n<\/span><\/li>\n- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n
- Single Threaded :\u00a0<\/strong> As the resources are not blocked therefore, multiple clients can be handled by a single worker process.<\/li>\n<\/ul>\n
The following diagram represents the Nginx architecture :<\/p>\n
<\/p>\n
<\/a><\/p>\n<\/h2>\n<\/h2>\n<\/h2>\n<\/h2>\n
<\/p>\n
\u00a0<\/strong><\/p>\nPros and Cons<\/strong><\/em><\/span><\/h2>\nApache<\/span><\/h3>\n\u00a0Pros<\/em> :<\/strong><\/p>\n\n- Large number of Modules:\u00a0<\/strong>Apache been available since many years and \u00a0has a larger community base, therefore has lots of Open-source modules written to expand it’s functionality.<\/li>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Large number of Users :\u00a0<\/strong>Nearly 46% of all websites run on Apache.<\/li>\n<\/ul>\n
Cons<\/em> :<\/strong><\/p>\n\n- Less Secure<\/strong> than nginx.<\/span><\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
\u00a0<\/span><\/h5>\nNginx<\/span><\/h3>\nPros<\/em> :<\/strong><\/p>\n\n- Fast<\/strong> : It does not create a new process for each new request, therefore it becomes very fast.<\/span><\/li>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Easy Scalability:<\/strong>\u00a0Nginx is highly scalable, and it’s performance is not dependent on hardware.<\/li>\n<\/ul>\n\n
Cons<\/em>:<\/strong><\/p>\n\n- Does not support Operating Systems<\/strong> like OpenVMS and IBMi.<\/span><\/li>\n
- Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
<\/p>\n<\/div>\n
\u00a0Conclusion\u00a0<\/strong><\/em><\/span><\/h2>\nWith the above advantages in mind, more and more people are moving towards Nginx. Even WordPress.com was shifted over to Nginx and they have thousands of servers, serving thousands of requests per second. Also Nginx has become the number 1 web server for the top 10,000 websites on the internet (Read more<\/a>).<\/p>\n <\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
\nWhat is Nginx and Apache
\n
\nNginx (Pronounced Engine-x) and Apache, both are open source web servers.
\nThe Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem\u00a0and some performance and scalability issues associated with Apache. … <\/p>\n
- \n
- Event Driven :\u00a0<\/strong>The starting and completion of events are marked by notifications, therefore the resources can be used by the other process until a process start or completion notification is received.
\n<\/span><\/li>\n- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n
- Single Threaded :\u00a0<\/strong> As the resources are not blocked therefore, multiple clients can be handled by a single worker process.<\/li>\n<\/ul>\n
The following diagram represents the Nginx architecture :<\/p>\n
<\/p>\n
<\/a><\/p>\n<\/h2>\n
<\/h2>\n
<\/h2>\n
<\/h2>\n
<\/p>\n
\u00a0<\/strong><\/p>\n
Pros and Cons<\/strong><\/em><\/span><\/h2>\n
Apache<\/span><\/h3>\n
\u00a0Pros<\/em> :<\/strong><\/p>\n
- \n
- Large number of Modules:\u00a0<\/strong>Apache been available since many years and \u00a0has a larger community base, therefore has lots of Open-source modules written to expand it’s functionality.<\/li>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Large number of Users :\u00a0<\/strong>Nearly 46% of all websites run on Apache.<\/li>\n<\/ul>\n
Cons<\/em> :<\/strong><\/p>\n
- \n
- Less Secure<\/strong> than nginx.<\/span><\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
\u00a0<\/span><\/h5>\n
Nginx<\/span><\/h3>\n
Pros<\/em> :<\/strong><\/p>\n
- \n
- Fast<\/strong> : It does not create a new process for each new request, therefore it becomes very fast.<\/span><\/li>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Easy Scalability:<\/strong>\u00a0Nginx is highly scalable, and it’s performance is not dependent on hardware.<\/li>\n<\/ul>\n
\nCons<\/em>:<\/strong><\/p>\n
- \n
- Does not support Operating Systems<\/strong> like OpenVMS and IBMi.<\/span><\/li>\n
- Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
<\/p>\n<\/div>\n
\u00a0Conclusion\u00a0<\/strong><\/em><\/span><\/h2>\n
With the above advantages in mind, more and more people are moving towards Nginx. Even WordPress.com was shifted over to Nginx and they have thousands of servers, serving thousands of requests per second. Also Nginx has become the number 1 web server for the top 10,000 websites on the internet (Read more<\/a>).<\/p>\n
<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
\nWhat is Nginx and Apache
\n
\nNginx (Pronounced Engine-x) and Apache, both are open source web servers.
\nThe Apache web servers are the oldest ones around. They have been in use since 1995, whereas nginx came some where around 2002. Both the products are open-source and free but if you need support for nginx you will need to buy Nginx Plus version. Nginx was written primarily to address the C10K problem\u00a0and some performance and scalability issues associated with Apache. … <\/p>\n - Limited support:\u00a0<\/strong>The Nginx community is not as big as the Apache community and it is repetitively newer as compared to Apache, so the community is also smaller for now.<\/li>\n<\/ul>\n
- Lightweight<\/strong> : As Nginx comes only with the core features required by the server, it makes it lightweight in comparison to Apache and hence consumes less memory as well.<\/li>\n
- Requires a heavy server configuration<\/strong> to handle high traffic websites. Since it spawns new process threads for each request, Apache requires a high memory footprint.<\/li>\n<\/ul>\n
- Open Source :\u00a0<\/strong> Everything \u00a0relating to Apache is free, be it there modules or there support.<\/li>\n
- Asynchronous :\u00a0<\/strong>Threads can be run concurrently, thus they do not block each other.<\/li>\n