Routing Laravel Package

Technical Evaluation

Architecture Fit

The Symfony Routing component is a highly mature, battle-tested solution for URL routing in PHP/Laravel ecosystems. It aligns well with Laravel’s dependency injection (DI) container, service container, and PSR-15 middleware patterns. Key strengths:

• Decoupled design: Works independently of frameworks (e.g., Laravel, Symfony) but integrates seamlessly via adapters.
• Performance: Optimized for compiled route matching (e.g., UrlMatcher with pre-compiled routes).
• Flexibility: Supports attribute-based routing (via annotations/attributes), YAML/JSON/PHP config, and dynamic route generation.
• Security: Actively patched for CVE vulnerabilities (e.g., regex injection, path traversal).
• Extensibility: Pluggable route loaders, matchers, and generators (e.g., custom constraints, requirements).

Laravel-Specific Fit:

• Laravel’s router (Illuminate\Routing\Router) already uses Symfony’s routing under the hood (via symfony/routing).
• No reinvention needed: This package is already a dependency in Laravel (indirectly via symfony/http-kernel).
• Opportunity for standardization: Could unify routing logic across Laravel + non-Laravel PHP microservices in a monorepo.

Integration Feasibility

Key Integration Points:

1. Replace Laravel’s Router (Partial):
   • Use UrlMatcher for request → route resolution.
   • Use UrlGenerator for route → URL generation (replaces route('name') helpers).
2. Attribute Routing:
   • Leverage Symfony’s [Route] attribute (via symfony/routing v8+) for modern PHP 8+ routing.
3. Dynamic Routes:
   • Load routes from YAML/JSON/PHP (e.g., config/routes.php) instead of Laravel’s routes/web.php.
4. Middleware:
   • Bind Symfony’s RouteCollection to Laravel’s middleware pipeline via Route::addRequirement().

Technical Risk

Critical Questions:

1. Why replace Laravel’s router? (Performance? Standardization? Feature parity?)
2. How will API versioning (e.g., /v1/) be handled? (Subdomains? Path prefixes?)
3. Will this introduce a new config format? (YAML/JSON vs. Laravel’s PHP routes)
4. How will middleware be bound to Symfony routes? (Laravel’s RouteServiceProvider vs. Symfony’s RouteCollection)
5. What’s the rollback plan if issues arise? (Fallback to Laravel’s default router)

Integration Approach

Stack Fit

Recommended Stack:

• PHP 8.1+ (for attribute routing).
• Symfony Routing v8+ (for modern features like [Route] attributes).
• Laravel 10+ (for compatibility with Symfony’s latest routing).

Migration Path

Phase 1: Pilot (Low Risk)

1. Add Symfony Routing as a Dependency:

   composer require symfony/routing
   

2. Create a Hybrid Router:
   • Extend Laravel’s Router to delegate to UrlMatcher for specific routes.
   • Example:

     $routeCollection = new RouteCollection();
     $routeCollection->add('blog_show', new Route('/blog/{slug}', ['controller' => BlogController::class]));
     $matcher = new UrlMatcher($routeCollection, new RequestContext());
     $parameters = $matcher->match('/blog/test');
     

3. Test in Isolation:
   • Use in a non-critical module (e.g., admin panel).
   • Benchmark performance vs. Laravel’s default router.

Phase 2: Full Integration (Medium Risk)

1. Replace Laravel’s Router:
   • Override Illuminate\Routing\Router with a custom class that uses RouteCollection.
   • Example:

     class SymfonyRouter extends Router {
         public function getRoutes() {
             return $this->routeCollection; // Symfony's RouteCollection
         }
     }
     

2. Migrate Route Definitions:
   • Convert routes/web.php to YAML/JSON/PHP config (e.g., config/routes.yaml).
   • Example (config/routes.yaml):

     blog_show:
         path: /blog/{slug}
         controller: App\Controller\BlogController
         methods: [GET]
     

3. Update URL Generation:
   • Replace route('name') with UrlGenerator:

     $generator = new UrlGenerator($routeCollection, $context);
     $url = $generator->generate('blog_show', ['slug' => 'test']);
     

4. Attribute Routing (PHP 8+):
   • Decorate controllers with [Route]:

     #[Route('/blog/{slug}', name: 'blog_show')]
     public function show(string $slug) { ... }
     

Phase 3: Deprecation (High Risk)

1. Deprecate Laravel’s Route Class:
   • Issue deprecation warnings for Route::get().
   • Redirect to Symfony’s Route class.
2. Remove Legacy Config:
   • Drop support for routes/web.php in favor of config/routes.yaml.
3. Full Symfony Routing Adoption:
   • Remove Laravel’s router entirely; rely solely on RouteCollection.

Compatibility