Symfony Kernel Laravel Package

Product Decisions This Supports

• Symfony Ecosystem Expansion: Enables integration of Symfony’s kernel (HTTP request/response cycle, dependency injection, event dispatching) into non-Symfony PHP projects, particularly Laravel applications needing Symfony’s advanced features (e.g., HTTP middleware, caching, security).
• Feature Roadmap: Justifies building a hybrid Laravel/Symfony app if the roadmap includes:
  • Symfony-specific components (e.g., Mercure, UnhandledExceptionListener, or HttpCache).
  • Legacy Symfony codebases requiring gradual migration to Laravel.
  • Microservices where Symfony’s kernel handles HTTP concerns while Laravel manages business logic.
• Build vs. Buy: Avoids reinventing Symfony’s kernel functionality (e.g., custom middleware stacks, request/response lifecycle) when the package provides a lightweight, MIT-licensed alternative.
• Use Cases:
  • API Gateways: Use Symfony’s kernel for request validation/routing while Laravel handles domain logic.
  • Hybrid Monoliths: Merge Laravel’s ORM (Eloquent) with Symfony’s HTTP layer for incremental modernization.
  • Testing/DevOps: Leverage Symfony’s KernelInterface for consistent testing environments across PHP frameworks.

When to Consider This Package

• Adopt if:
  • Your project requires Symfony’s kernel but is primarily Laravel-based (e.g., for middleware, HTTP caching, or security components).
  • You need interoperability between Symfony and Laravel (e.g., sharing controllers, services, or events).
  • The package’s MIT license aligns with your open-source policy, and its low stars/score (but active maintenance) don’t pose a risk.
  • You’re evaluating Symfony’s HttpFoundation or EventDispatcher without full framework migration.
• Look elsewhere if:
  • You need full Symfony framework support (use Symfony Flex or Symfony CLI instead).
  • The package lacks Laravel-specific integrations (e.g., Eloquent, Laravel’s service container).
  • Your team lacks Symfony expertise to debug kernel-level issues.
  • Alternatives like API Platform or Laravel’s built-in middleware suffice for your use case.

How to Pitch It (Stakeholders)

For Executives: "This package lets us leverage Symfony’s battle-tested HTTP kernel—middleware, caching, and security—in our Laravel app, without rewriting core infrastructure. It’s a low-risk way to adopt Symfony’s strengths (e.g., for API gateways or hybrid architectures) while keeping Laravel’s ecosystem. The MIT license and lightweight design make it easy to integrate, and it future-proofs our stack for potential Symfony migrations."

For Engineering: *"The dpoposki/symfony-kernel bundle bridges Laravel and Symfony by wrapping Symfony’s KernelInterface in a Laravel-compatible bundle. Key benefits:

• Reuse Symfony middleware (e.g., Cors, Security) in Laravel routes.
• Share HTTP logic between frameworks (e.g., shared controllers for APIs).
• Avoid vendor lock-in: MIT license, no Symfony framework dependency. Tradeoff: Requires Symfony knowledge for advanced use cases, but ideal for incremental adoption. Let’s prototype a shared middleware stack for our [X] API to validate."*