Simple Bus Bridge Bundle Laravel Package

Product Decisions This Supports

• Event-Driven Architecture (EDA) Adoption: Enables seamless integration of Symfony’s UserBundle with SimpleBus (a messaging library) to decouple user-related workflows (e.g., authentication, profile updates) from direct service calls. Aligns with roadmaps for scalable, modular microservices or CQRS patterns.
• Build vs. Buy: Justifies buying (reusing) this lightweight bridge over custom development for teams already using Symfony + SimpleBus, reducing boilerplate for event dispatching (e.g., UserCreated, PasswordResetRequested).
• Use Cases:
  • Asynchronous workflows: Trigger background jobs (e.g., sending welcome emails) when user events occur.
  • Audit logging: Decouple user actions (e.g., UserUpdated) from business logic via message queues.
  • Legacy integration: Bridge older Symfony apps to modern event-driven systems without rewriting core logic.

When to Consider This Package

• Avoid if:
  • Your team uses non-Symfony frameworks (e.g., Laravel, Django) or alternative messaging libraries (e.g., RabbitMQ, AWS SQS plugins).
  • You need active maintenance (last release: 2017); evaluate forks or modern alternatives like symfony/messenger.
  • Your architecture doesn’t require event-driven user workflows (e.g., simple CRUD apps).
  • You’re using PHP < 5.5 or Symfony < 2.8 (check compatibility risks).
• Look elsewhere if:
  • You need built-in queue support (this bundle requires separate queue setup).
  • You prefer type safety (SimpleBus lacks modern PHP 8+ features; consider Laravel’s Horizon or Symfony Messenger).
  • Your team lacks Symfony/SimpleBus expertise (steep learning curve for setup).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us decouple user-related actions (e.g., signups, password resets) from our core services using event-driven messaging—reducing direct dependencies and enabling scalable background processing. For example, when a user registers, we can instantly queue an email welcome task without blocking the request. It’s a low-risk, high-reward way to adopt modern architecture patterns with minimal dev effort, leveraging existing Symfony/SimpleBus investments."

For Engineering: *"If we’re already using Symfony + SimpleBus, this bundle cuts 30–50% of the boilerplate needed to wire user events (e.g., UserBundle entities) to message handlers. Key benefits:

• Zero custom glue code for event dispatching (e.g., user_created → queue).
• Tested with PHPSpec (BDD-friendly for critical workflows).
• MIT-licensed, so no legal blockers. Tradeoff: Last updated in 2017, but the core pattern (Symfony + SimpleBus) is stable. We’d need to validate queue setup (e.g., Redis, Doctrine transport) separately."*

For Developers: *"This is a 5-minute install if you’re already using:

composer require bengor-user/simple-bus-bridge-bundle

Then configure UserBundle events to publish to SimpleBus channels. Example:

// Dispatch a 'UserCreated' event to the queue
$event = new UserCreatedEvent($user);
$this->bus->handle($event); // SimpleBus processes it asynchronously.

Pro tip: Pair with Symfony’s EventDispatcher for hybrid sync/async workflows."*