StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. PHP-FPM vs nginx

PHP-FPM vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
PHP-FPM
PHP-FPM
Stacks121
Followers119
Votes0

PHP-FPM vs nginx: What are the differences?

Introduction

PHP-FPM and nginx are both important components in web servers. Understanding their key differences can help in choosing the right setup for websites and applications.

  1. Execution Model: PHP-FPM is a process manager for PHP which handles PHP script execution and management of workers. It communicates with the web server (like nginx) using FastCGI protocol. On the other hand, nginx is a high-performance web server and reverse proxy server that can also act as an HTTP cache. It can handle static content efficiently and can also forward dynamic requests to PHP-FPM.

  2. Architecture: PHP-FPM follows a pool or worker model where multiple dedicated worker processes handle incoming PHP requests. Each worker process can handle multiple requests simultaneously using threads or processes. On the other hand, nginx uses an asynchronous and event-driven architecture where a single master process handles all incoming requests efficiently without blocking multiple connections.

  3. Resource Handling: PHP-FPM primarily handles PHP scripting and processing, including database connections, session management, and application logic. It depends on the web server (like nginx) to handle static file requests efficiently. Nginx, on the other hand, excels at serving static files due to its efficient architecture. It can handle static content without the need to involve PHP-FPM for processing.

  4. Load Balancing: PHP-FPM supports load balancing by using multiple worker processes. It can distribute requests across different PHP-FPM instances, ensuring efficient resource utilization and increased performance. Nginx also supports load balancing, but at a higher level. It can distribute requests to backend servers (including PHP-FPM instances) using various load balancing algorithms like round-robin, IP-hash, etc.

  5. Caching: PHP-FPM does not provide built-in caching mechanisms. However, it can integrate with other caching solutions like Varnish or a Content Delivery Network (CDN) to improve performance. Nginx, on the other hand, includes a built-in caching module that can cache responses from dynamic requests. It can cache content in memory, on disk, or even on a distributed cache server like Redis.

  6. Configuration and Extensibility: PHP-FPM configuration involves settings related to PHP execution, process management, and resource limits. It can be tweaked to achieve optimal performance based on specific application requirements. Nginx provides rich configuration options for customizing server behavior, handling server blocks, SSL/TLS settings, and more. It also supports various modules for additional functionality like URL rewriting, gzip compression, rate limiting, and more.

In summary, PHP-FPM is responsible for executing PHP scripts and managing worker processes, while nginx acts as a powerful web server, reverse proxy, and can handle static content efficiently. PHP-FPM excels at processing PHP requests, while nginx is effective at serving static files and load-balancing requests. Both technologies have their strengths and can be used together to achieve high-performance web applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on NGINX, PHP-FPM

greg00m
greg00m

Mar 9, 2020

Needs advice

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities.
Ready, aim fire!

766k views766k
Comments
jlp78
jlp78

May 31, 2019

ReviewonNGINXNGINX

I use nginx because it is very light weight. Where Apache tries to include everything in the web server, nginx opts to have external programs/facilities take care of that so the web server can focus on efficiently serving web pages. While this can seem inefficient, it limits the number of new bugs found in the web server, which is the element that faces the client most directly.

727k views727k
Comments
StackShare
StackShare

May 29, 2019

Needs advice

From a StackShare Community member: "We are a LAMP shop currently focused on improving web performance for our customers. We have made many front-end optimizations and now we are considering replacing Apache with nginx. I was wondering if others saw a noticeable performance gain or any other benefits by switching."

725k views725k
Comments

Detailed Comparison

NGINX
NGINX
PHP-FPM
PHP-FPM

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.

Statistics
GitHub Stars
28.4K
GitHub Stars
-
GitHub Forks
7.6K
GitHub Forks
-
Stacks
115.0K
Stacks
121
Followers
61.9K
Followers
119
Votes
5.5K
Votes
0
Pros & Cons
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
No community feedback yet

What are some alternatives to NGINX, PHP-FPM?

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Sidekiq

Sidekiq

Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Beanstalkd

Beanstalkd

Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

lighttpd

lighttpd

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase