Here's How You Can Architect Advanced Routing Patterns in Symfony

If you ask a junior developer what the Symfony Routing component does, they will tell you it maps a URL to a controller. They aren’t wrong, but they are only scratching the surface. For a Senior Developer or Architect, the Routing component is the nervous system of the application. It is the first line of defense, the primary content negotiator, and the mechanism that transforms a stateless HTTP request into a stateful domain context. In Symfony 7, the ecosystem has matured significantly. We have moved past the era of massive routes.yaml files and annotation-heavy controllers. The modern standard leverages PHP 8.3+ attributes, strict typing, and immutable data structures to create routing logic that is self-documenting and highly performant. routes.yaml This article explores advanced routing scenarios. We aren’t looking at how to create a /contact page. We are looking at how to build multi-tenant SaaS platforms, secure temporary access systems, and database-driven CMS architectures using the latest Symfony 7 standards. how to build multi-tenant SaaS platforms secure temporary access systems, database-driven CMS architectures Prerequisites & Environment To follow these examples, assume a standard Symfony 7.x (targeting 7.3 features) environment running PHP 8.3. Composer Dependencies: { "require": { "php": ">=8.3", "symfony/framework-bundle": "^7.0", "symfony/routing": "^7.0", "symfony/expression-language": "^7.0", "symfony/uid": "^7.0", "symfony/validator": "^7.0" } } { "require": { "php": ">=8.3", "symfony/framework-bundle": "^7.0", "symfony/routing": "^7.0", "symfony/expression-language": "^7.0", "symfony/uid": "^7.0", "symfony/validator": "^7.0" } } The “CMS Problem”: Dynamic Route Loaders One of the most common architectural hurdles in large applications is handling dynamic routes. If you are building a CMS, an e-commerce platform with custom slugs, or a system where users define their own URLs, you cannot define these routes in static config files. You need a Custom Route Loader. Custom Route Loader In Symfony 7, routes are cached aggressively. This means we can load routes from a database without hitting the DB on every request — only when the cache is warmed. The Implementation We will create a loader that fetches “Pages” from a database and registers them as routes. namespace App\Routing;

use App\Repository\PageRepository; use Symfony\Bundle\FrameworkBundle\Routing\Attribute\AsRoutingLoader; use Symfony\Component\Config\Loader\Loader; use Symfony\Component\Routing\Route; use Symfony\Component\Routing\RouteCollection;

#[AsRoutingLoader] final class DatabaseRouteLoader extends Loader { private bool $isLoaded = false;

public function __construct( private readonly PageRepository $pageRepository, private readonly string $env ) { parent::__construct(); }

public function load(mixed $resource, ?string $type = null): RouteCollection { if ($this->isLoaded === true) { throw new \RuntimeException('Do not add the "database" loader twice'); }

$routes = new RouteCollection(); // In PROD, this runs only during cache warmup. // In DEV, this might run more often depending on config. $pages = $this->pageRepository->findAllActiveRoutes();

foreach ($pages as $page) { $defaults = [ '_controller' => 'App\Controller\Cms\PageController::show', 'id' => $page->getId(), '_title' => $page->getTitle(), // Metadata accessible in the controller ];

$requirements = [ // Enforce trailing slash policy or regex constraints here 'slug' => '[a-z0-9\-]+', ];

$route = new Route( path: '/' . $page->getSlug(), defaults: $defaults, requirements: $requirements, methods: ['GET'] );

// Unique route name is critical $routeName = 'cms_' . $page->getSlug(); $routes->add($routeName, $route); }

$this->isLoaded = true;

return $routes; }

public function supports(mixed $resource, ?string $type = null): bool { return 'database' === $type; } } namespace App\Routing;