Dispatcher Bundle Laravel Package

Product Decisions This Supports

• Decoupling Business Logic: Enables modular design by separating event dispatching logic from core application workflows, improving maintainability and scalability for microservices or large-scale monolithic apps.
• Roadmap for Event-Driven Architecture: Accelerates adoption of event-driven patterns (e.g., real-time notifications, workflow orchestration) without reinventing event dispatching infrastructure.
• Build vs. Buy: Avoids custom event bus development (e.g., Symfony Messenger alternatives) while offering lightweight, PHP-native integration.
• Use Cases:
  • Real-Time Systems: Push notifications, live updates (e.g., chat apps, dashboards).
  • Background Processing: Offload tasks (e.g., email queues, analytics) without blocking requests.
  • Cross-Service Communication: Decouple services in a microservices ecosystem via shared events.
  • Legacy System Modernization: Gradually introduce event-driven logic into monolithic PHP apps.

When to Consider This Package

• Adopt if:

  • Your team uses Symfony/Laravel and needs a simple, PHP-native event dispatcher with minimal setup.
  • You prioritize GPL-2.0 compliance (open-source friendly) and require no external dependencies (e.g., RabbitMQ, Redis).
  • Your use case fits synchronous event handling (not async workers like Laravel Queues).
  • You lack resources to build a custom event bus but need basic pub/sub functionality.

• Look Elsewhere if:

  • You need asynchronous processing (e.g., delayed jobs, retries) → Use Laravel Queues or Symfony Messenger.
  • You require scalable distributed event buses (e.g., Kafka, NATS) → Evaluate Pheanstalk, Enqueue, or custom solutions.
  • Your team uses non-Symfony/Laravel PHP → This bundle is Symfony-centric.
  • You need advanced event routing (e.g., filtering, transformations) → Consider EventSauce or ReactPHP.

How to Pitch It (Stakeholders)

For Executives: "This package lets us adopt event-driven architecture without heavy infrastructure costs. By decoupling components (e.g., notifications, payments), we reduce technical debt and enable faster feature delivery. It’s a low-risk way to modernize our PHP stack—think of it as ‘Symfony’s built-in event bus’ for teams that want simplicity over scalability."

For Engineering: *"Pros:

• Zero setup: Drops into Symfony/Laravel with a single bundle install.
• Lightweight: No external services; pure PHP implementation.
• Symfony-native: Integrates with existing DI, services, and event listeners.

Trade-offs:

• Not for async: If you need background jobs, pair with Laravel Queues.
• Limited scalability: Best for single-process or small clusters (no distributed pub/sub).

Use Case: Replace ad-hoc event(new MyEvent()) calls with a structured dispatcher—ideal for prototyping or small-scale event-driven flows. For production-grade async, we’d need to evaluate [Symfony Messenger] or [Laravel Queues]."*

Note: Package’s low stars/maturity suggest vetting for critical systems; ideal for internal tools or MVPs.