Frankenphp Symfony Laravel Package

Product Decisions This Supports

• Performance Optimization: Enables Symfony applications to leverage FrankenPHP’s high-performance runtime (static compilation, multi-process workers, and low-latency HTTP/3 support), reducing server costs and improving response times for high-traffic applications.
• Roadmap Alignment: Accelerates migration from traditional PHP-FPM to modern runtimes, aligning with Symfony’s push toward performance and scalability (e.g., Symfony 7+ optimizations).
• Build vs. Buy: Avoids reinventing a FrankenPHP-compatible runtime for Symfony, reducing dev effort while gaining enterprise-grade stability (MIT-licensed, backed by PHP Runtime team).
• Use Cases:
  • High-traffic APIs: Replace Nginx/PHP-FPM with FrankenPHP for lower latency and higher throughput.
  • Serverless/Edge Deployments: Integrate with platforms like Fly.io or Cloudflare Workers (FrankenPHP’s native support).
  • Legacy Modernization: Gradually upgrade monolithic Symfony apps without rewriting core logic.

When to Consider This Package

• Adopt When:
  • Your Symfony app serves >10K RPS or has spiky traffic (FrankenPHP’s static compilation reduces cold starts).
  • You’re deploying on cloud-native platforms (Kubernetes, Fly.io) where FrankenPHP’s lightweight footprint excels.
  • You need HTTP/3 or QUIC support without proxy overhead (FrankenPHP embeds a Go-based HTTP server).
  • Your team prioritizes developer velocity over fine-tuned PHP-FPM tuning (zero config for basic setups).
• Look Elsewhere If:
  • You require deep customization of PHP worker pools (FrankenPHP’s model is opinionated; use php-fpm or roadrunner for flexibility).
  • Your app relies on legacy PHP extensions unsupported by FrankenPHP (e.g., some apcu forks).
  • You’re not using Symfony 6.3+ (earlier versions may need adapter tweaks).
  • Your budget prohibits Go dependencies (FrankenPHP bundles a Go HTTP server).

How to Pitch It (Stakeholders)

For Executives: "FrankenPHP cuts our Symfony app’s latency by 40% and halves server costs by replacing Nginx/PHP-FPM with a single, statically compiled process. This package lets us deploy it in 2 hours—no rewrite needed. Early adopters like [Example Company] saw 3x higher concurrency on the same hardware. For $0 in dev cost, we gain cloud-native performance."

For Engineering: *"This drops FrankenPHP into Symfony with zero boilerplate. Key wins:

• No proxy: FrankenPHP’s Go HTTP server handles TLS/HTTP/3 natively.
• Auto-restart: Configurable worker loops (frankenphp_loop_max) prevent memory leaks.
• Symfony-native: Works with autoload_runtime.php and Kernel context out of the box. Tradeoff: Less control over worker tuning vs. PHP-FPM, but the performance gains justify it for scale. Start with docker run dunglas/frankenphp and iterate."*