Shulou(Shulou.com)06/01 Report--

This article mainly explains "what is the difference between Nginx and Apache". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the difference between Nginx and Apache".

Nginx, like Apache, is HTTP server software. It adopts modular structure design in function implementation, and supports common language interfaces, such as PHP, Perl, Python, etc., as well as forward and reverse proxies, virtual hosts, URL rewriting, compressed transmission, SSL encrypted transmission and so on.

The main difference between Apache and NGINX is their design architecture. Apache uses a process-driven approach and creates a new thread for each request. NGINX uses an event-driven architecture to handle multiple requests in a thread.

What is an Apache HTTP server?

Apache HTTP server is an open source cross-platform Web server, also known as "httpd" and Apache. He is the Apache Software Foundation that manages its brand and services. The server is developed and maintained by the open developer community under ASF. Apache, which runs mainly on Linux, supports 46 per cent of the world's websites. It is a key component of the LAMP (Linux, Apache, MySQL, PHP) stack.

What is a NGINX Web server?

What is NGINX? What is the pronunciation? It is pronounced "Engine X" and it is the Web server released by Igor Sissoyev in 2004. Today, it is more than just a web server! At first, most people used Nginx as a supplement to Apache. It is mainly used to provide static files, but today it has evolved into a complete Web server that handles the entire web server task. Nginx is often used as a reverse proxy, load balancer, mail proxy, and HTTP cache. Both Apache and Nginx are the most common web servers for Linux. Together, they serve more than 50% of network traffic.

Although Apache and NGINX have many qualities in common, they are different in many ways. Each excels in its own way and has its own uses and programs. To understand the differences and draw conclusions, let's go through the following detailed, end-to-end comparison. We also mentioned the winner of each comparison point at the end of each point.

Basic architecture

When it comes to Apache and Nginx, the fundamental difference lies in their design architecture. This means that they actually handle connections and traffic differently and respond to different traffic conditions. One is a process-driven approach and the other is an event-driven architecture.

Apache

A process-driven method that creates a new thread for each request. Apache adopts multithreading method. It provides a variety of processing modules. These pre-modules are basically three types of request processing algorithms. Each is used for different server requirements. MM (multiprocessing module) provides a flexible architecture for selecting different connections and different processing algorithms. In addition, different versions of Apache 2 use different parade modules. The three main Apache MM are: process (pre-fork) MPM, worker MPM, and event MPM. By default, Apache 2.2 is configured in pre-fork mode (mpm_prefork). It responds to a set of processes, each of which can process a single request at a time. In other words, Apache creates a new thread each time to process each connection request. A thread is the smallest sequence of programming instructions that can be independently managed by the scheduler. In most cases, a thread is a component of a process. However, the basic architecture of Apache can lead to significant resource consumption and, therefore, problems with the server (such as slow speed).

Nginx

The event-driven approach processes multiple requests in a single thread, and Nginx uses an event-driven architecture and processes requests asynchronously. It is designed to use non-blocking event-driven connection processing algorithms. As a result, its process can handle thousands of connections (requests) in one processing thread. This connection process module enables Nginx to work quickly and widely with limited resources. In addition, you can use Nginx on low-power systems and on systems running under heavy loads.

The winner is NGiNX-its structure is lightweight and its architecture is much faster than Apache. Performance in terms of Apache vs Nginx, the two Web servers handle static and dynamic content differently. They say Nginx is better at dealing with static content, let's see if it's true!

Static content

Apache

Static content is provided using a file-based approach, and static content or files are usually files, such as CSS files, JavaScripts files, or images, stored on disk on the server computer. Apache uses its traditional file-based approach to static content.

Nginx

Nginx is the big brother when it comes to providing static content. Because Nginx's design architecture is more capable of handling load, it is much faster in providing static content. According to a benchmark of up to 1000 simultaneous connections, its performance is 2.5 times faster than that of Apache. Nginx serves static resources, and PHP does not need to know this. Apache, on the other hand, processes all these requests with expensive overhead. This makes Nginx more efficient and requires less system resources.

This small image shows static content requests that are processed in seconds. Nginx obviously surpasses Apache here!

Dynamic content

Apache

Apache can handle dynamic content in the Web server itself without relying on any external components. So, it can deal with yourself. Talk about Apache vs Nginx performance: when considering dynamic content processing, Nginx (if not better) is almost equal. The following is a comparison of the number of dynamic content requests. There is no difference in appearance.

Nginx

It does not deal with dynamic content, and when it comes to dynamic content, Nginx cannot handle dynamic content in a Web server like Apache does. All requests with dynamic web content are passed to an external process, such as PHP-FPM, for execution. Nginx waits for the final content to be returned and delivered to the client. For clear ideas, refer to this image:

When used with SCGI processors and FastCGI modules, NGINX can provide services for dynamic content. Static: in terms of static content, Nginx beats Apache. Dynamic: both are good at dealing with dynamic content.

Operating system support

Operating system support may be an important point to consider, especially when comparing Apache with Nginx. But the two of them are almost alike here.

Apache

Supports all the same systems as Unix, including Linux and BSD. It fully supports MS-WindowsApache running on a variety of systems like Unix (such as Linux or BSD), and fully supports Microsoft Windows.

Nginx

Almost all operating systems like Unix are supported. Windows is partially supported. It also runs on several modern Unix systems and has some support for Windows, but its Windows performance is not as powerful as other platforms.

The winner is Apache who wins here.

Distributed / centralized configuration

Apache vs Nginx is a well-deserved topic. Their configuration makes them different from each other and makes them equally interesting. Let's see whose configuration is easier and faster.

Apache

Additional configurations are allowed on a per-directory basis through the .htaccess file. This architecture allows unprivileged users to control certain aspects of their Web site without granting them permission to edit the master configuration. This is big!

Nginx

No other configuration is allowed, on the other hand, it has a drawback. It does not provide other configurations. However, it benefits you because it increases performance. By not allowing directory configuration, it can provide requests faster than Apache. It does not need to search the .htaccess file and interpret the user-created req.

Winner: if you consider configuration, you can do Apache;. If you consider configuration, you can do APache. If the speed is NGinx.

Request for explanation

In the Apache vs Nginx debate, the method of interpreting requests is an interesting topic for comparison. They all process and interpret requests in completely different ways.

Their different ways make them unique and make one a little better than the other. Let's explore!

Apache

Pass the location of the file system, providing the ability to interpret requirements. As a physical resource in the location of the file system, a more abstract assessment may be required. It passes the request as a file system location.

Of course, Apache does use URI locations, but they are usually used for more abstract resources. When creating or configuring a virtual host, Apache uses a directory block under the document root.

You can also see this preference for file system locations when you overwrite a specific directory configuration with an .htaccess file.

Nginx

The request is interpreted through URI, and Nginx is created as a Web server and a reverse proxy server. Due to the requirements of these architectures, Nginx mainly uses your eyes. Convert to a system if necessary. It does not provide a mechanism for specifying configurations. For a file system directory, pass its URI itself. Passing the request (URI) instead of the file system location makes it easy for Nginx to run in Web and proxy servers. It is simply configured by how the layout responds to the differential request pattern.

It does not check the file system until it is ready for a request for the service and explains why it does not implement any form of .htaccess file. This design of interpreting requests as URI locations makes it easy for Nginx to act not only as a Web server, but also as a proxy server, load balancer, and HTTP cache.

In addition, in the Apache vs Nginx competition, NGINX won again in terms of the transfer rate (the speed at which data is sent from the server to the client). In most cases, Nginx won with a fair amount of 500 Universe.

Winner: it seems that Nginx won because it explained and reacted faster.

Function module

Both are expandable through the module system. But the way they work is different. Let's compare the functional modules of two Web servers: Apache vs Nginx!

Apache

60 official modules that can be loaded dynamically and can be turned on / off the Apache server has a rich set of features that can be enabled by installing one of the 60 official modules. There are many other unofficial modules that can be easily found on the Internet.

Its module system allows you to dynamically load or unload modules to meet your needs. Its module can be turned on or off to add or remove functions and connect to the primary server.

In short, Apache has several functional modules to meet your needs, but many modules are not used very often.

Nginx

Third-party core module (not dynamically loaded) on the other hand, Nginx is selected and compiled into a third-party plug-in process. Cannot be loaded dynamically. These modules are useful, but they allow you to decide what to get from the server by including only the functionality you want to use. It is considered much more secure than the Apache server because any component can connect in the server. In addition, NGINX provides all the core functions of the Web server without sacrificing the lightweight and high-performance features required for success. Apache is like Microsoft Word,Nginx, like notepad. Apache has a million options, but you only need a few. Nginx does these "a few" things 50 times faster than Apache.

Winner: NGiNX-it's not very important, but features and modules make it a lighter, smarter, better Web server than Apache.

Flexibility

Flexibility is one of the most important issues for Web servers. There are some interesting differences in Apache vs Nginx flexibility.

Apache

Support for customizing the Web server through dynamic modules. You can customize the Web server through the riding module. Apache's dynamic modules take the longest time to load, so all Apache modules support this feature.

Nginx

Not flexible enough to support dynamic modules and loading. However, this is not the case with NGINX. In early 2016, NGINX received dynamic module loading support; previously, NGINX required administrators to compile modules into NGINX binaries. Most modules do not yet support dynamic loading, but over time, they may support dynamic loading. Winner: Apache-it clearly takes the lead on this point.

Safety

Apache vs Nginx security has once again become a controversial topic. Well, both Web servers provide excellent extended security for C-based code bases.

Apache

It's perfectly safe. Apache ensures that all websites running on its servers are secure and free from any harm or hacker attacks. Therefore, it provides configuration tips for handling DDoS attacks, as well as mod_evasive modules for responding to HTTP DoS, DDoS, or brute force attacks.

NGINX

The least amount of code for better security. However, NGINX's code base is clearly several orders of magnitude smaller, so from a forward-looking security perspective, this is definitely a big advantage. NGINX also lists recent security recommendations. Read an article on the Nginx blog about defending against DDoS attacks. Winner: Nginx-, it is considered safer.

Support

Support is what every customer yearns for. It can change or destroy your user experience. There doesn't seem to be much difference when comparing Apache and Nginx support.

Apache

Community support is done through mailing lists, IRC, and stack overflows. Commercial Apache support is available from many third-party companies, such as OpenLogic, but the Apache Foundation does not maintain the official list. The Apache server is designed to provide strong support for all its users.

Nginx

Provide community support through mailing lists, IRC, stack overflows, and forums. The company behind NGINX offers a commercial product called NGINX Plus, which supports a set of additional features related to load balancing, media streaming, and monitoring.

Winner:! The support for both is almost the same. Both Web servers are great.

In the end

Neither Apache nor nginx can be replaced by each other. They have their strengths and weaknesses. After understanding the benefits, limitations, and differences, you probably have the idea that works best for your Web server.

In our post about Apache versus Nginx, 5 out of 9 points were won by Nginx and 2 points were "tied" by Apache and nginx. Therefore, we can clearly see that NGINX is ahead of Apache.

When did you choose Apache over Nginx?

I) Apache.

NGINX does not support .htaccess files similar to Apache. However, with Apache, you can gain the advantage of giving unprivileged users control over some important aspects of their Web site.

Obviously, users are not allowed to edit the master configuration. Using the .htaccess file, you can override system-wide settings on a per-directory basis. For best performance, include these .htaccess directives in the main configuration file. In a shared managed environment, Apache works better because of its .htaccess configuration. P.S. Keep the best choice for dedicated hosts or VPS Nginx.

Ii) in case of functional limitations = use Apache

Nginx has some very important core modules. However, Nginx has some functional limitations.

If there are some limitations or need to use additional modules that Nginx does not support, you may need to choose Apache instead.

When do you choose Nginx over Apache?

I) Fast static content processing

Nginx can do a better job of handling static files from specific directories.

In addition, upstream server processes are not blocked because of the large number of static content requests, because Nginx can handle them at the same time. This significantly improves the overall performance of the back-end server.

Nginx constantly strives to provide users with a better experience. In 2018, it showed significant growth. Browse the main points of 2018 on the Nginx blog.

Ii) is very suitable for high-traffic websites

If we talk about the speed and how many customers can serve under high loads, Nginx will always shine as a winner over Apache.

This makes Nginx significantly lightweight and ideal for server resources. This is why most Web developers prefer Nginx to Apache.

In particular, today's e-stores employ a Magento developer who knows how to work on high-traffic websites and is good at working on Nginx.

In short, when it comes to serving a website with a lot of traffic, there is no beating Nginx.

Or use at the same time

At the same time, by using the advantages of each server together, you can use them.

You can use the Nginx in front of the Apache as a server proxy (as shown in the following figure). This takes advantage of the fast processing speed of Nginx and the ability to establish large no connections at the same time.

For static connections, Nginx quickly serves the files to the client. For dynamic content, such as Php files, the Nginx reverse proxy server proxies their requests to Apache, and Apache can then process their results and return their rendered pages.

Nginx can then pass the final content to the client. In addition, it allows you to have a very practical web server to serve your customers (a large number of users) very quickly.

Thank you for your reading, the above is the content of "what is the difference between Nginx and Apache". After the study of this article, I believe you have a deeper understanding of the difference between Nginx and Apache, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.