PHP-FPM, (g)unicorn, Puma and uWSGI — will no longer be needed
summary
Overview of how common app servers like PHP-FPM, Gunicorn/Unicorn, uWSGI, Puma (and sometimes Apache) are used together with nginx to run PHP, Python, and Ruby web apps, and why those traditional combos may become unnecessary. Describes alternatives or architectural shifts that remove the need for these dedicated application servers and the implications for deploying high-load web services.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:24What is EnginX
- 6:57Why EnginX
- 11:21Shared memory and speed
- 13:08Queue and timeout issues
- 20:35Solution: LIFO queue
- 23:50Adaptive processing mode
- 24:55Monitoring and isolation
- 26:43Unified server config
- 28:10Future plans
- 33:15Summary and outlook
- 35:26Q&A
related talks
01h 04mI saw the future, and its web servers were written in PHP
58muWSGI, the Swiss Army (MacGyver) knife of deployment
48mGive your PHP apps superpowers with FrankenPHP
41mGoodbye LAMP Stack?
25mUnderstanding Ruby Web Server Internals: Puma, Falcon, and...
31mHey, Python-Web-Community! What's going on?
45mPHP is the king ...
33mRunning PHP-Applications in a Multi-Process Container