Panel Discussion
summary
Debate focuses on practical tradeoffs: asynchronous PHP works for daemons and niche use cases but needs ReactPHP and an end-to-end async stack (dispatcher, DB drivers, APIs) to pay off; most apps are fine under 5s so synchronous PHP on PHP7 remains pragmatic. Serverless fits some flows but cold-starts and language/runtime behavior (Lambda) matter. Functional adoption hits a real blocker: two-phase function lookup and case-insensitivity. Doctrine’s unit-of-work shows memory and complexity limits; many switch to event sourcing plus raw SQL or alternatives like Atlas.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:00Asynchronous
- 7:00Serverless
- 12:45Favorite Programming Language
- 15:20Other Languages
- 15:50Favorite Language
- 21:15Alternatives
- 23:10Question
related talks
32mAsynchronous PHP
51mFunctionality and Asynchronicity in PHP7
50mImproving Application Performance with ReactPHP
37mLet's Program Like It's 1999
46mPushing the limits of PHP with React PHP
33mAn Introduction to Asynchronous PHP using ReactPHP
25mAsync PHP with Coroutines: Building Scalable Applications
49mPanel Discussion: The Future of PHP