Async Event Dispatcher Bundle Laravel Package

Product Decisions This Supports

• Decoupling Event-Driven Workflows: Enables asynchronous processing of events (e.g., notifications, analytics, background jobs) without blocking user requests, improving system responsiveness and scalability.
• Roadmap for Performance Optimization: Ideal for projects where synchronous event dispatching (e.g., via Symfony’s EventDispatcher) creates bottlenecks (e.g., high-traffic APIs, batch processing).
• Build vs. Buy: Avoids reinventing async event infrastructure (e.g., custom RabbitMQ/Kafka integrations) when lightweight, PHP-native async is sufficient.
• Use Cases:
  • User Onboarding: Trigger async emails/SMS after signup without delaying the flow.
  • Data Pipelines: Process large datasets (e.g., CSV imports) via async events.
  • Microservices: Decouple services by offloading cross-service events to a queue.
  • Legacy System Integration: Gradually migrate synchronous event listeners to async.

When to Consider This Package

• Adopt When:

  • Your Symfony app uses EventDispatcher heavily and synchronous listeners cause latency.
  • You need a simple, PHP-native async solution (no need for Redis/RabbitMQ setup).
  • Your event workload is moderate (not high-throughput; config limits consumers to 4 by default).
  • You’re okay with basic reliability (no built-in retries, dead-letter queues, or monitoring).

• Look Elsewhere If:

  • You need enterprise-grade reliability (e.g., retries, circuit breakers, or distributed tracing).
  • Your events require complex routing (e.g., dynamic queues, priority-based processing).
  • You’re already using message brokers (e.g., RabbitMQ, Pulsar) and want tighter integration.
  • You need horizontal scaling beyond the bundle’s maximum_num_of_consumers limit.
  • The project is archived (low maintenance risk; consider alternatives like symfony/messenger or reactphp).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us offload time-consuming event tasks (e.g., notifications, analytics) to the background, making our app faster and more scalable—without adding complexity. It’s like adding a ‘background worker’ for Symfony events, but with minimal setup. Perfect for improving user experience during peak loads or reducing server costs by processing heavy tasks asynchronously."

For Engineers: *"A lightweight wrapper around Symfony’s EventDispatcher that pushes events to a PHP-based queue (likely using ReactPHP under the hood). Key benefits:

• Zero infrastructure: No Redis/RabbitMQ needed—just install and configure.
• Simple API: Replace dispatch($event) with dispatchAsync($event) in your code.
• Configurable: Control concurrency (num_messages_per_execution, maximum_num_of_consumers).
• Symfony-native: Works seamlessly with existing event listeners. Tradeoff: Basic reliability (no retries/monitoring), but great for prototyping or low-risk async use cases. For production-critical workloads, we’d need to evaluate alternatives like symfony/messenger."*

For DevOps: "Minimal operational overhead—just a Composer package and YAML config. Runs consumers as PHP processes (likely via ReactPHP event loop). No external dependencies beyond Symfony. Monitor via standard logging (no built-in metrics dashboard)."