Amp Laravel Package

amphp/amp

AMPHP (AMP) accelerates PHP concurrency with fibers, eliminating callbacks and generators. Built on PHP 8.1’s cooperative coroutines, it lets you run async tasks like sync code—ideal for I/O-bound apps. Use Amp\async() for parallel execution and Future::await() to handle results seamlessly. No event...

Technical Evaluation

Architecture fit: Limited fit for Laravel's synchronous request lifecycle. Best suited for isolated async tasks (e.g., CLI commands, queue workers) rather than core HTTP request handling. Laravel's middleware/controller stack isn't designed for fiber-based concurrency, creating structural misalignment.
Integration feasibility: Feasible for specific non-core use cases (e.g., concurrent HTTP requests via amphp/http-client, non-blocking DB queries). Requires careful scoping to avoid disrupting Laravel's synchronous flow. Not viable for replacing fundamental framework components like routing or ORM.
Technical risk: High risk of blocking the main process if event loop isn't properly managed. Potential conflicts with blocking I/O in existing Laravel packages (e.g., standard PDO database drivers). Web server compatibility issues (PHP-FPM/Apache/Nginx not designed for long-running event loops).
Key questions: How will the event loop lifecycle be managed within Laravel's request/response cycle? Which specific components would benefit? How to handle compatibility with Laravel's synchronous DB/query builders? Can the team maintain separate async execution contexts without destabilizing the app?

Integration Approach

Stack fit: Only suitable for targeted I/O-bound operations in isolated contexts (e.g., background