Eventor Symfony Laravel Package

Product Decisions This Supports

• Decoupling Microservices: Enables event-driven architecture by abstracting pub/sub operations, reducing tight coupling between services.
• Roadmap for Scalability: Supports future expansion into distributed systems by leveraging Dapr’s portable pub/sub API, aligning with cloud-native strategies.
• Build vs. Buy: Avoids reinventing pub/sub infrastructure, opting for a lightweight, maintained library instead of custom development.
• Use Cases:
  • Real-time notifications (e.g., user activity, system alerts).
  • Asynchronous workflows (e.g., order processing, background jobs).
  • Cross-service communication in microservices ecosystems.

When to Consider This Package

• Adopt if:

  • Your Symfony/Laravel app needs a minimal, broker-agnostic pub/sub layer (currently Dapr-only).
  • You prioritize event-driven architecture over REST for scalability or resilience.
  • Your team lacks expertise in building pub/sub systems from scratch.
  • You’re already using Dapr or evaluating it for microservices.

• Look elsewhere if:

  • You need multi-broker support (e.g., RabbitMQ, Kafka, Redis) out of the box.
  • Your team requires enterprise-grade features (e.g., dead-letter queues, schema validation).
  • You’re constrained by the lack of community adoption (0 stars, no dependents).
  • Your project demands active maintenance (last release: 2022).

How to Pitch It (Stakeholders)

For Executives: "This lightweight library abstracts pub/sub operations, enabling event-driven communication between services—reducing latency, improving scalability, and cutting development time. By leveraging Dapr’s portable API, we future-proof our architecture for cloud-native deployments while avoiding vendor lock-in. Minimal overhead means faster iteration."

For Engineering: "eventor-symfony provides a clean, Symfony-compatible pub/sub abstraction for Dapr, with built-in OpenTelemetry tracing and W3C-compliant headers. It’s ideal for decoupling services, handling async workflows, or integrating with Dapr’s pub/sub API. Trade-offs: limited to Dapr for now, but the minimalist design makes it easy to extend."