React Functions Laravel Package

Product Decisions This Supports

• Asynchronous API/Service Layer: Enables non-blocking I/O for high-throughput microservices or APIs (e.g., real-time data processing, WebSocket integrations, or event-driven architectures).
• Performance Optimization: Justifies adoption for latency-sensitive applications (e.g., chat apps, live dashboards, or IoT data pipelines) where blocking calls degrade UX.
• Build vs. Buy: Avoids reinventing non-blocking wrappers for PHP’s built-in functions (e.g., file_get_contents, curl_exec, exec), reducing dev time and technical debt.
• Roadmap for Scalability: Aligns with plans to migrate from synchronous to event-driven systems (e.g., replacing Guzzle HTTP clients with ReactPHP equivalents).
• Multi-Protocol Support: Enables unified async handling for HTTP, WebSockets, or custom protocols in a single codebase (leveraging ReactPHP’s ecosystem).
• PHP 8.1/8.2 Compatibility: Supports modern PHP stacks, reducing friction for teams adopting newer versions.

When to Consider This Package

• Avoid if:
  • Your app is CPU-bound (this library focuses on I/O, not parallelism).
  • You need blocking operations (e.g., batch processing without real-time constraints).
  • Your stack is fully synchronous (e.g., legacy monoliths with no async requirements).
  • You’re using alternative async frameworks (e.g., Swoole, Amp) with incompatible APIs.
• Consider if:
  • You’re building real-time features (e.g., notifications, collaborative editing).
  • Your team already uses ReactPHP or plans to adopt it for event loops.
  • You need lightweight, composable async utilities (no heavy dependencies).
  • Your PHP version is 8.1+ (for Promise v3 support).
  • You want to reduce callback hell with Promise-based APIs.

How to Pitch It (Stakeholders)

For Executives: "This package lets us rewrite blocking I/O operations (like HTTP calls or file reads) as non-blocking, cutting latency and scaling our real-time features—think WebSocket APIs or live updates—without rewriting core logic. It’s a drop-in upgrade for ReactPHP users, with MIT licensing and PHP 8.2 support, so it’s low-risk and future-proof."

For Engineering: *"Drift’s reactphp-functions gives us battle-tested, non-blocking wrappers for PHP’s standard functions (e.g., file_get_contents, curl_exec) using ReactPHP’s event loop. It’s ideal for:

• Async APIs: Replace Guzzle with ReactPHP’s HttpClient + this library.
• Performance: Handle 10K+ concurrent connections without thread pools.
• Simplicity: Promise-based API reduces nested callbacks vs. raw ReactPHP. Downside: Minimal adoption (0 dependents), but the ReactPHP ecosystem is mature. Start with the demo to validate fit."*

For Architects: *"This fills a gap in PHP’s async ecosystem by providing a thin, standardized layer over ReactPHP’s primitives. Key tradeoffs:

• Pros: Lightweight, PHP 8.2-compatible, integrates with ReactPHP’s Promise system.
• Cons: No built-in retries/timeouts (add via ReactPHP’s Timeout or libraries like react/promise-timer). Recommendation: Pilot in a non-critical async service (e.g., a WebSocket gateway) before full adoption."*