Simple Bus Bridge Bundle Laravel Package

Product Decisions This Supports

• Event-Driven Architecture (EDA) Adoption: Enables seamless integration of Symfony applications with SimpleBus (a PHP messaging library) to decouple services via command/event buses, reducing tight coupling in microservices or modular monoliths.
• Legacy System Modernization: Bridges older Symfony 2.8+ applications to modern event-driven patterns without full rewrite, leveraging FileBundle for file-based persistence of messages.
• Build vs. Buy: Buy for teams already using FileBundle or needing lightweight, file-backed message queues (vs. building custom solutions or adopting RabbitMQ/Kafka).
• Use Cases:
  • Background job processing (e.g., order fulfillment, notifications).
  • Decoupled service communication (e.g., user auth → payment processing).
  • Audit trails or event sourcing with file persistence.
• Roadmap Alignment: Supports future-proofing for Symfony 6+ (if maintained) or migration to newer messaging libraries (e.g., Symfony Messenger) via abstraction layers.

When to Consider This Package

• Avoid If:
  • High Throughput Needed: File-based storage lacks scalability for high-volume messaging (consider Symfony Messenger + Doctrine/Redis).
  • Modern Symfony: Prefer Symfony Messenger (native, actively maintained) for Symfony 4.4+.
  • No FileBundle Dependency: Overhead of adding FileBundle for minimal messaging needs.
  • Critical Reliability: No guarantees for message durability/retries (vs. RabbitMQ, AWS SQS).
  • Active Maintenance: Last release in 2018; evaluate fork risk or migration path.
• Consider If:
  • Using Symfony 2.8–4.3 with FileBundle for persistence.
  • Need a simple, file-backed message bus without external dependencies.
  • Prototyping event-driven workflows before committing to heavier infrastructure.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us adopt event-driven architecture with minimal risk—integrating Symfony with SimpleBus via file storage to decouple services (e.g., orders, payments) without upfront investment in message queues. Ideal for modernizing legacy systems or prototyping workflows before scaling. Low cost, but requires monitoring for maintenance gaps."

For Engineers: "A lightweight bridge to use SimpleBus (a battle-tested PHP messaging library) in Symfony, backed by FileBundle for persistence. Perfect if you’re already using FileBundle or need a no-ops message bus for development/testing. Tradeoff: file storage limits scalability, but avoids RabbitMQ/Kafka complexity. Symfony Messenger is the long-term alternative for production."

Key Asks:

1. Architecture Team: Align on event-driven goals vs. immediate needs.
2. DevOps: Assess file storage limits for message volume.
3. Lead Dev: Evaluate migration path if Symfony 5+ is targeted.