Pubsub Router Bundle Laravel Package

Product Decisions This Supports

• Decoupling Event-Driven Logic: Enables clean separation of Pub/Sub channels (e.g., RabbitMQ, Kafka, Redis Streams) from business logic, reducing tight coupling in microservices or monolithic Symfony apps.
• Scalable Event Routing: Accelerates roadmap items requiring dynamic event handling (e.g., real-time notifications, workflow automation) by abstracting routing logic into reusable components.
• Build vs. Buy: Justifies buying this package over custom development for teams lacking Pub/Sub expertise, as it provides battle-tested routing, matching, and generation features out-of-the-box.
• Use Cases:
  • Event-Driven Architectures: Route messages from queues/topics to Symfony services/controllers without manual switch-case logic.
  • Legacy System Integration: Bridge legacy systems emitting events to modern Symfony apps via standardized routing.
  • Multi-Tenant SaaS: Dynamically route events per tenant using configurable channel-to-logic mappings.

When to Consider This Package

• Adopt if:

  • Your Symfony app uses Pub/Sub (e.g., RabbitMQ, AWS SNS/SQS) and lacks a centralized event router.
  • You need to reduce boilerplate for mapping channels to business logic (e.g., on('order.created', OrderHandler::class)).
  • Your team prioritizes maintainability over custom routing solutions (last release: 2022, but actively supported 2.x).
  • You’re using Symfony 4.4–6.0 (check compatibility table).

• Look elsewhere if:

  • You require real-time Pub/Sub (e.g., WebSockets) beyond message queues—this is queue-focused.
  • Your stack isn’t Symfony (e.g., Laravel, Node.js)—consider alternatives like Laravel’s Events or custom middleware.
  • You need advanced event transformation (e.g., schema validation, retries)—pair with a dedicated library like Symfony Messenger.
  • Your team lacks Symfony familiarity—steepness of learning curve may outweigh benefits.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us route Pub/Sub messages to business logic automatically, cutting development time for event-driven features by 30–50%. For example, instead of manually wiring up a RabbitMQ queue to an OrderService, we define a simple route (channel.order_created → OrderHandler). This reduces tech debt, speeds up feature delivery (e.g., real-time notifications), and aligns with our microservices roadmap. Low risk—MIT-licensed, actively maintained, and used in production by the Symfony community."

For Engineering: *"The PubSubRouterBundle solves our pain point of spaghetti event handlers by centralizing routing logic. Key wins:

• Declarative routes: Define channel-to-handler mappings in YAML/XML/PHP (e.g., channel.order.created: [App\Handler\OrderCreatedHandler]).
• Symfony integration: Works seamlessly with DI, Messenger, and HTTP clients.
• Extensible: Supports custom matchers/generators for complex routing (e.g., tenant-aware queues). Tradeoff: Minimal learning curve if you’re familiar with Symfony bundles. Recommendation: Pilot in a non-critical module (e.g., notifications) to validate ROI before full adoption."*