PHP Superpowers with FrankenPHP

Transcript

1. Mario Blažek PHP Superpowers with @phpanarchist
2. About me • Mario Blažek • Backend Team Lead @4ofthem • Married with children • Believes in Open Source • Zagreb PHP Meetup organizer (ZgPHP) • Chief Fire O ffi cer
3. What kind of PHP setup are you using?
4. Existing setups • Apache + mod_php • Apache + php-fpm • Nginx + php-fpm • Standalone PHP servers (ReactPHP, Swoole, RoadRunner) • FrankenPHP
5. Nginx • Event-driven architecture, handles thousands of concurrent requests e ff i ciently • Serves static fi les directly without passing requests to PHP • Load balancing and reverse proxy capabilities • Handles concurrent connections better than traditional web servers
6. php-fpm (FastCGI Process Manager) • Handles dynamic PHP requests separately from the web server • Uses process pools (static, dynamic, ondemmand) to e ff i ciently manage multiple requests • Provides better security by isolating PHP execution from the web server • Allows tuning of worker processes, memory limits, and timeouts for performance optimization • Communicates with Nginx via FastCGI protocol
7. php-fpm tunning • https://tideways.com/pro fi ler/blog/an-introduction-to-php-fpm-tuning
9. Container philosophy • One process per container • Stateless and disposable containers
10. Problems with nginx+fpm • Process model challenges • Inter-process communication overhead • Complex scaling • Resource consumption • Deployment complexity
11. Franken to the game • PHP application server based on Caddy web server • One service! • Two modes: classic + worker • 103 Early Hints support • HTTP2 and HTTP3 native support
12. Franken to the game • Developed by Kévin Dunglas • Symfony Core member • API Platform • Mercure • Vulcain
13. Caddy web server • Modern and fast (event-driven, non- blocking architecture) • Caddy fi le - user friendly con fi guration • Automatic HTTPS • Works seamlessly as a reverse proxy, LB, cache and request forwarder • First-class support for PHP
14. Static binary
15. Docker
16. New SAPI
17. Caddy con fi guration Caddy fi le
18. Superpower - worker mode • Boot your application once • Keep it in memory • Process incoming requests without having to boot your application again • Relies on goroutines and channels • Symfony Runtime compatible • Some resemblance with RoadRunner
19. Worker mode
20. Symfony Runtime • Abstracts the application bootstrap logic into runtimes • Front controller remains generic • Basically application remains decoupled from the infrastructure • Di ff erent runtimes provided by community
21. Without Runtime
22. With Runtime
23. Symfony in worker mode
24. Early hints
25. Early hints
26. Mercure
27. Mercure
28. Benchmarks
29. Benchmarks • https://dev.to/dimdev/performance-benchmark-of-php-runtimes-2lmc • https://medium.com/beyn-technology/wars-of-symfony-runtimes-a- performance-odyssey-7b0120e8f9e1 • https://frankenphp.dev/docs/performance/ • https://github.com/dunglas/frankenphp-demo/tree/main/benchmark
30. Questions?
31. Thank you! https://bit.ly/phpfrankensuperpowers