Weave Code
Event Store Bus Bridge Laravel Package
prooph/event-store-bus-bridge
prooph/event-store-bus-bridge integrates prooph/event-store with prooph/service-bus, forwarding committed domain events to message bus subscribers. It helps wire event sourcing and messaging in PHP applications while keeping storage and bus concerns decoupled.
Marry CQRS with Event Sourcing
Frequently asked questions about Event Store Bus Bridge
- What does prooph/event-store-bus-bridge do?
- It integrates prooph/event-store with prooph/service-bus by listening for committed event-store appends and forwarding those domain events to a message producer. In practice it is thin glue for CQRS and event-sourcing write-side wiring, not a full framework.
- How do I install prooph/event-store-bus-bridge in Laravel?
- Install it with Composer alongside prooph/event-store and prooph/service-bus, then register the bridge services in a Laravel service provider. The package is framework-agnostic and does not provide Laravel auto-discovery, so you must wire the EventPublisher, event store, and message producer manually.
- Is prooph/event-store-bus-bridge compatible with Laravel 10 or 11?
- There is no official Laravel integration, so compatibility depends on the underlying prooph packages and your PHP version. The bridge is PSR-oriented and can be hosted in Laravel, but the 2021 release line may pin older PHP constraints; run composer why-not before committing.
- Which PHP versions does prooph/event-store-bus-bridge support?
- The available release history is old, with a 2021-08-26 release likely capping at PHP 8.0. Current Laravel versions generally require PHP 8.1 or later, so verify constraints with Composer for your exact dependency set. Do not assume PHP 8.2 or 8.3 support without checking.
- How do I forward committed domain events to Laravel's queue?
- Implement Prooph\Common\Messaging\MessageProducer as a thin adapter over Laravel's event dispatcher or queue. The bridge's EventPublisher listens on EventStore::EVENT_APPEND_TO and passes committed domain events to that producer. This adapter is the cleanest seam for Laravel integration.
- Do I need prooph/event-store and prooph/service-bus to use this bridge?
- Yes. The bridge has no independent value without prooph/event-store for persistence and prooph/service-bus for command and event routing. Adopting it means accepting prooph's message, aggregate, and repository abstractions alongside Eloquent.
- Is prooph/event-store-bus-bridge suitable for production event sourcing?
- It can be used in production only if you have deliberately adopted prooph's CQRS/ES model and accepted the ecosystem risk. The package is small and auditable, but the prooph ecosystem is effectively in maintenance mode with a small user base. Evaluate correctness, PHP upgrade paths, and operational support before relying on it.
- Does the TransactionManager prevent dual-write problems with external brokers?
- No. The TransactionManager wraps command handling in an event-store transaction, but it cannot make publication to an external broker or durable queue atomic with the database commit. You can still publish events that are later rolled back or commit events that are never published. Treat it as transaction scoping, not a true outbox.
- How should I test event publication with this bridge?
- Unit-test your MessageProducer adapter against Laravel's dispatcher or queue fake, then integration-test that appending to the event store triggers the EventPublisher and reaches the producer. Keep the event store test backend separate from production and assert committed events only. Also test rollback behavior so publication expectations are explicit.
- What are alternatives to prooph/event-store-bus-bridge in Laravel?
- Consider ecotone/ecotone for Laravel-aware CQRS/ES, spatie/laravel-event-sourcing for a lighter idiomatic approach, or event-engine if you are following prooph's author. If you only need this bridge's behavior, roughly 200 lines of in-house glue may be a lower-risk option.
Weaver
How can I help you explore Laravel packages today?