Weave Code
Broadway Bundle Laravel Package
macnificos/broadway-bundle
Symfony bundle for Broadway event sourcing that wires command and event buses, event stores, read models, and sagas into the container, reducing boilerplate when building CQRS and event-driven PHP applications.
Symfony bundle for broadway/broadway
Frequently asked questions about Broadway Bundle
- Does macnificos/broadway-bundle work with Laravel?
- No. It is a Symfony bundle that depends on Symfony's kernel booting a Bundle subclass and loading service definitions through DI extension classes, and Laravel does not boot Symfony bundles. Composer may still install it because it is an ordinary library, which can give a false impression that integration succeeded. In practice none of its buses, event stores, or handler registration will be wired into a Laravel application.
- How do I install macnificos/broadway-bundle in a Laravel app?
- There is no supported installation path. Running composer require macnificos/broadway-bundle may resolve, but the package's YAML and XML service definitions are loaded by Symfony's container, not Laravel's service provider system. To get the same behavior in Laravel you would need to reimplement the wiring yourself, so installing this package adds a dependency without reducing effort.
- Is macnificos/broadway-bundle actively maintained?
- No. The last release was in August 2019, roughly six years ago, and the repository shows zero stars and zero dependents. That release predates Symfony 5, 6, and 7 as well as PHP 8, so expect deprecation noise at best and hard type or constructor failures at worst. There is no community triage or production validation behind it.
- What are the Laravel alternatives to macnificos/broadway-bundle?
- The strongest Laravel-native option is spatie/laravel-event-sourcing, which is actively maintained and provides Eloquent-backed projections. Framework-agnostic options include patchlevel/event-sourcing and eventsauce/eventsauce, both of which target modern PHP. You can also use broadway/broadway directly with your own Laravel service provider if you specifically want Broadway's API.
- Can I use broadway/broadway directly in Laravel without this bundle?
- Yes. Broadway itself is framework-agnostic, so the practical path is to require broadway/broadway and write an EventSourcingServiceProvider that binds the event store, command bus, event bus, serializers, and read-model repositories into Laravel's container. You would also register any console commands in Laravel's console kernel and add a config file for driver selection such as Doctrine DBAL, MongoDB, or an in-memory store for tests. Budget roughly three to five engineer-days including a spike.
- Which Laravel versions are supported by macnificos/broadway-bundle?
- None officially. The package is built for Symfony applications and has no Laravel service provider, configuration file, or facade. Any Laravel version compatibility you see is incidental from Composer resolving shared Symfony components, not from actual framework integration.
- What Symfony and PHP versions does macnificos/broadway-bundle require?
- The 2019 release implies PHP 7.x constraints and Symfony 3.4 or 4.x-era dependency injection configuration. Under PHP 8.1 and newer you should expect deprecations or hard failures, and under modern Symfony the bundle would not compile cleanly. It has not been updated for current Symfony or Doctrine DBAL releases.
- How does macnificos/broadway-bundle register command and event handlers?
- It uses Symfony's dependency injection tags and YAML configuration to auto-configure Broadway buses and register command handlers, event subscribers, and query handlers as tagged services. That mechanism is entirely Symfony-specific. In Laravel you would instead use Laravel's container tagging or explicit bindings inside a service provider.
- Does macnificos/broadway-bundle support event stores and read-model projections in Laravel?
- It configures pluggable event stores and read-model projections only through Symfony DI extension classes. There is no Laravel integration, so nothing will be registered in a Laravel app. Under Laravel you would either use Eloquent-backed projections from a package like spatie/laravel-event-sourcing or bind a Doctrine DBAL or MongoDB event store yourself.
- Is it worth forking macnificos/broadway-bundle for a Laravel project?
- Only if your team specifically requires Broadway's exact API surface. Forking means rewriting the DI extension classes as a Laravel service provider, dropping the Bundle class, updating for PHP 8 and current Doctrine DBAL, and owning maintenance indefinitely. For most teams a maintained alternative such as spatie/laravel-event-sourcing or patchlevel/event-sourcing is lower cost and lower risk.
Weaver
How can I help you explore Laravel packages today?