Messagebus Bundle Laravel Package

Product Decisions This Supports

• Decoupling Microservices/Modules: Enables asynchronous communication between Laravel services, reducing tight coupling and improving modularity. Aligns with a roadmap toward microservices or domain-driven design (DDD).
• Event-Driven Architecture: Facilitates real-time data flow (e.g., notifications, analytics, workflows) without polling or direct API calls, reducing latency and improving scalability.
• Build vs. Buy: Justifies buying (reusing) a lightweight, PHP-native solution over building a custom RabbitMQ/Kafka integration or adopting a heavier framework (e.g., Symfony Messenger).
• Use Cases:
  • Internal Systems: Order processing, payment confirmations, or inventory updates where events must propagate reliably.
  • Third-Party Integrations: Decoupling external API calls (e.g., payment gateways) to handle failures gracefully.
  • Background Jobs: Replacing queues (e.g., Laravel Queues) for complex workflows requiring retries, dead-letter queues, or event sourcing.
  • Legacy Modernization: Gradually introducing event-driven patterns into monolithic Laravel apps.

When to Consider This Package

Adopt if:

• Your Laravel app needs asynchronous, decoupled communication between services/modules.
• You’re using PHP/PHP-based microservices and want to avoid JavaScript/Go-based tools (e.g., Kafka, NATS).
• Your team prefers lightweight, bundle-based solutions over standalone services (e.g., RabbitMQ).
• You require basic message bus features (publish/subscribe, retries, dead-letter queues) without heavy configuration.
• Your stack is Laravel-centric (Symfony compatibility may require extra work).

Look elsewhere if:

• You need high-throughput, distributed messaging (e.g., Kafka, Redis Streams) for IoT or real-time analytics.
• Your team lacks PHP expertise but has strong Go/JavaScript skills (consider NATS, RabbitMQ, or Pulsar).
• You require advanced features like exactly-once delivery, multi-tenancy, or cross-language support (e.g., gRPC).
• Your budget allows for managed services (e.g., AWS SQS, Google Pub/Sub) with built-in scalability.
• You’re already using Symfony Messenger and want deeper integration with Symfony’s ecosystem.

How to Pitch It (Stakeholders)

For Executives: "This package lets us replace slow, synchronous API calls between our Laravel services with a fast, reliable message bus—like sending emails in the background instead of waiting for each step to finish. It’s lightweight, PHP-native, and reduces costs by avoiding external queue services. For example, when a user places an order, we can instantly notify shipping and analytics teams without blocking the checkout flow. It’s a low-risk way to modernize our architecture while keeping costs down."

For Engineers: *"BobrD’s MessageBusBundle is a minimal, Laravel-friendly wrapper for PHP’s react/promise and php-amqplib (AMQP/RabbitMQ). It gives us:

• Publish/subscribe for event-driven workflows (e.g., OrderCreated → trigger SendEmail, UpdateInventory).
• Retry logic and dead-letter queues for failed messages (no more lost jobs).
• Zero config for basic use cases; easy to extend for custom transports (e.g., Redis, database).
• No vendor lock-in: Under the hood, it’s just AMQP—we can swap transports later if needed.

Pros: Faster than custom solutions, no new languages/tools. Cons: Limited to PHP; not a silver bullet for high-scale systems. Let’s prototype it for our order-processing pipeline first."*