Domain Event Dispatcher Bundle Laravel Package

Product Decisions This Supports

• Event-Driven Architecture (EDA) Adoption: Enables teams to implement domain-driven design (DDD) patterns by decoupling event publishing from consumption, reducing tight coupling between services.
• Microservices Roadmap: Facilitates eventual consistency and asynchronous workflows, critical for scaling systems into microservices.
• Build vs. Buy: Avoids reinventing event dispatching logic, saving dev time while maintaining flexibility for custom event types.
• Use Cases:
  • Real-time notifications (e.g., user actions triggering emails/SMS).
  • Audit logging or analytics pipelines.
  • Workflow orchestration (e.g., order processing with deferred steps).
  • Cross-cutting concerns (e.g., caching invalidation, search index updates).

When to Consider This Package

• Adopt if:

  • Your team uses Symfony 2.3–3.0 (compatibility constraint).
  • You need a lightweight, DDD-aligned event system without heavy frameworks (e.g., Laravel’s built-in events).
  • Deferred events (async processing) are a priority, leveraging Symfony’s kernel.terminate.
  • You want Symfony Profiler integration for debugging event flows.
  • Your architecture tolerates singleton-based dispatching (centralized control).

• Look elsewhere if:

  • You’re on Symfony 4+ or Laravel (package is outdated; consider native alternatives).
  • You need advanced event sourcing (e.g., replayability, persistence).
  • Your team prefers reactive streams (e.g., RxPHP) over synchronous dispatching.
  • You require high-throughput event processing (this is single-threaded).
  • You need modern PHP 8+ features (package targets PHP 5.5+).

How to Pitch It (Stakeholders)

For Executives: "This package lets us implement event-driven workflows—like notifications or background jobs—without building custom infrastructure. It’s a lightweight, battle-tested way to decouple services, reduce complexity, and enable async processing (e.g., sending emails after an order is placed). Think of it as ‘fire-and-forget’ for business logic, improving scalability and maintainability. Low risk: it’s a MIT-licensed Symfony bundle with minimal overhead."

For Engineers: *"This wraps DomainEventDispatcher for Symfony, giving us:

• DDD-friendly events: Publish domain events from entities, listen via tagged services.
• Deferred dispatching: Events fire at kernel.terminate (configurable) for async workflows.
• Symfony Profiler: Debug event flows with a visual map.
• No bloat: Singleton-based, no external dependencies beyond Symfony. Tradeoff: Outdated (2017), but works for Symfony 2/3. If we’re locked into that stack, it’s a quick win for EDA. For newer stacks, we’d evaluate Laravel’s events or ReactPHP."*