Swoole: Issues and Production Use
summary
Migration of a real marketplace from a traditional PHP stack to an asynchronous Swoole-based architecture is described, using PHP 8, Swoole coroutines/fibers and a concurrent HTTP server. The talk covers practical benefits and operational problems encountered integrating Postgres, Redis, RabbitMQ and Doctrine into the asynchronous ecosystem.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:07Monolith scaling issues
- 4:23Horizontal scaling problems
- 6:12Swoole solved issues
- 8:18HTTP server setup
- 9:45HTTP server modes
- 13:25Superglobal variables issues
- 15:54Global state management
- 18:53Doctrine memory leaks
- 21:23Async theory
- 25:25Coroutines mechanism
- 27:32PHP coroutines examples
- 31:07Non-blocking I/O clients
- 32:30Concurrency in project
- 34:38Connection pool issues
- 36:24Memory leaks fixes
- 38:10Swoole client driver problems
- 38:51Swoole crons timers
- 41:18Cron infrastructure
- 43:07Tool compatibility
- 44:34Doctrine integration issues
- 46:00Migration performance
- 48:51Resource savings
- 50:18PHP version support
- 51:00Error handling
- 52:46Symfony Messenger integration
- 53:28Summary Q&A
related talks
38mBuilding Server Applications with Swoole
35mSpeed up web APIs with Expressive and Swoole
40mMezzio + Swoole
25mAsync PHP with Coroutines: Building Scalable Applications
29mPanel Discussion
45mPHP is the king ...
50mSymfony Messenger: the sharpest tool in your PHP toolbox
43mAsync with Messenger, AMQP and Mercure