Http Kernel Laravel Package

Product Decisions This Supports

• Async API/Backend Services: Enables building high-performance, non-blocking HTTP services (e.g., real-time APIs, event-driven architectures) without rewriting core logic.
• Microservices & Decoupling: Facilitates splitting monolithic apps into async microservices by leveraging Symfony’s kernel with ReactPHP’s promise-based model.
• Roadmap for Scalability: Justifies investment in async infrastructure if current sync stack (e.g., Laravel) is a bottleneck for high-throughput workloads.
• Build vs. Buy: Avoids reinventing async HTTP handling; integrates with existing Symfony/Laravel ecosystems (shared middleware, routing, etc.).
• Use Cases:
  • WebSocket/real-time features (e.g., notifications, live updates).
  • High-frequency data processing (e.g., IoT, trading systems).
  • Serverless/edge computing where async reduces latency.

When to Consider This Package

• Adopt if:
  • Your app requires low-latency, high-concurrency (e.g., >10K RPS).
  • You’re already using Symfony/Laravel and want async without framework swaps.
  • Your team has ReactPHP/Promise experience (or is willing to upskill).
  • You need fine-grained control over request lifecycle (e.g., middleware per route).
• Look elsewhere if:
  • Your workload is CPU-bound (async won’t help; consider workers like Laravel Queues).
  • You lack async-aware dependencies (e.g., databases, third-party APIs).
  • Your team prefers simplicity over custom async architectures (e.g., Swoole, RoadRunner).
  • You’re constrained by vendor lock-in (no dependents = unproven ecosystem).

How to Pitch It (Stakeholders)

Executives: "This package lets us modernize our HTTP stack to handle 10x more traffic with the same servers—critical for [X growth goal]. By reusing our existing Symfony/Laravel codebase but adding async (via ReactPHP), we avoid costly rewrites while future-proofing for real-time features like [Y use case]. MIT license and DriftPHP’s backing reduce risk."

Engineering: "Symfony’s HttpKernel is battle-tested; this adds async via Promises, so we keep middleware, routing, and DI but gain non-blocking I/O. Demo shows [Z performance metric], and the skeleton repo provides a clear migration path from Laravel. Tradeoff: steeper learning curve for async patterns, but docs and ReactPHP’s maturity mitigate that."