Rabbitmq Simplebus Bundle Laravel Package

Product Decisions This Supports

• Async command/event architecture: Choosing whether to make write-side operations (commands) or domain events execute asynchronously via a message broker rather than in-process. This package is a concrete integration layer for that decision — it wires SimpleBus CommandBus/EventBus handlers to RabbitMQ queues and producers.
• CQRS / event-driven roadmap bets: If the roadmap includes eventual consistency, decoupled bounded contexts, or fan-out of domain events, this package represents one (dated) implementation pattern you can evaluate for scope and effort.
• Build vs. buy for messaging glue: The build option is "write our own RabbitMQ + bus integration." This package is the buy/borrow option — but at 11 stars, zero dependents, and a 2017 release, it mostly serves as a reference implementation to estimate the effort of the build path rather than a dependency to adopt.
• Technology stack validation: Its existence confirms that SimpleBus + RabbitMQ was a recognized pairing in the Sylius/Symfony ecosystem — useful context if stakeholders ask "has this been done before?"
• Migration/obsolescence planning: If a team already depends on this pattern, the decision this supports is when and how to migrate to a maintained alternative (e.g., Symfony Messenger), not whether to double down.

When to Consider This Package

Consider it (cautiously) when:

• You are already committed to SimpleBus as your command/event bus and to Symfony (this is a Symfony bundle, not Laravel-native — it will not drop into a Laravel app without adaptation).
• You need a worked example of how to bridge a bus to RabbitMQ — useful as an architectural reference or forkable starting point, not as a governed dependency.
• You have a legacy Sylius/Symfony codebase from ~2017–2019 where this bundle may already be in use and you need to understand its behavior before replacing it.

Look elsewhere when:

• You are on Laravel or modern Symfony. Use Symfony Messenger (native, actively maintained, first-class RabbitMQ/AMQP transport) or Laravel's native queue system with an AMQP driver.
• You need support, security patching, or SLAs. Last release 2017-11-10; no maintenance signal; no dependents means no community pressure to fix issues.
• You are building greenfield. Do not introduce an eight-year-old, low-adoption bridge as a core dependency; the total cost of ownership (upgrades, PHP version compatibility, abandoned transitive deps) dominates any time saved.
• You require observability, retries, dead-lettering, and schema evolution out of the box — modern alternatives provide these; this does not.

How to Pitch It (Stakeholders)

To executives:

This is a small, unmaintained open-source integration from 2017 that connects a PHP message bus to RabbitMQ. We should not adopt it as a dependency. Its value to us is as a reference pattern — it shows the shape of async command/event processing and lets us estimate the build effort. Adopting it would create upgrade and security risk with no community backing (11 stars, zero downstream dependents). Recommendation: treat as reference only; if we pursue async messaging, use a maintained, vendor-supported transport (e.g., Symfony Messenger or our framework's native queues) and budget a small spike rather than a dependency.

To engineering:

Treat sylius-labs/rabbitmq-simplebus-bundle as an architectural specimen, not a library. It demonstrates producer/consumer wiring between SimpleBus and RabbitMQ and is useful for scoping our own integration or for understanding legacy Sylius code. Expect to fork or reimplement rather than composer require. Modern equivalents (Symfony Messenger's AMQP transport, Enqueue, or Laravel's queue + AMQP driver) should be the default evaluation set for any new async-messaging work; this package is only defensible inside an existing SimpleBus/Symfony footprint, and even then only with a documented migration path off it.