- How do I install micro-module/broadway in a Laravel app?
- Install it with Composer using composer require micro-module/broadway. The package ships a Laravel service provider and a package configuration file, so after installing you publish the config and define your command bus, event bus and event store bindings. Because the published README is sparse, read the require block in its composer.json before installing so you know which Laravel and PHP versions it expects.
- Which Laravel and PHP versions does micro-module/broadway support?
- There has been no tagged release since July 2023, so its declared constraints most likely target the Laravel and PHP versions current at that time. Always inspect the composer.json require block instead of assuming compatibility with the newest Laravel release. If the repository publishes no CI matrix, verify the install in a throwaway branch before committing to an upgrade.
- Which broadway/broadway version does micro-module/broadway require?
- It is a thin integration layer over broadway/broadway, so its Composer constraint pins the underlying Broadway major version. That constraint becomes your ceiling: a package locked to an older Broadway line can block upgrades across the rest of the application. Check the constraint in composer.json and confirm it matches the Broadway release you intend to run in production.
- How do I configure the event store for Broadway in a Laravel application?
- The package provides configurable event store bindings, so you select between Broadway's Doctrine DBAL store, a MongoDB store, or the in-memory store used in tests. Configuration lives in the published package config file, where you point the container binding at your chosen store implementation. Keep your domain code typed against Broadway's EventStore interface so the backend can be swapped without touching aggregates.
- How do I register command handlers and event subscribers with Laravel's container?
- Register your command handlers and event subscribers in a service provider and let the package's container bindings resolve them into Broadway's CommandBus and EventBus. Handlers should take their dependencies through the constructor so Laravel's container does the wiring. Keep registration explicit rather than relying on auto-discovery, since Broadway's buses resolve handlers by the command or event class they handle.
- Does micro-module/broadway support read-model projections?
- Yes, configurable read-model projections are listed among its features, so projectors can listen to domain events and update read tables. Broadway itself leaves projection plumbing to the application, so expect to write the projector classes while the package supplies the container bindings. Design your UI for eventual consistency between the write model and the projections it reads.
- Is micro-module/broadway safe to use in production?
- Be cautious: the repository shows no stars, no dependents, no release since July 2023, and a single maintainer, so there is little downstream pressure to keep it compatible with new Laravel or PHP releases. That does not mean the code is poor, but it does mean your team owns the upgrade path and any security triage. Many teams treat packages in this state as a reference implementation to copy rather than a dependency to adopt.
- How do I test aggregates and the command bus with micro-module/broadway?
- The package includes testing helpers and container bindings that let you run an in-memory event store, so aggregates and command buses can be exercised without a database. The caveat is that test helpers often reach into Broadway internals, which are the least stable surface of the library, so pin exact versions. If the assertions rely on reflection rather than public interfaces, plan on maintaining a fork when Broadway changes.
- Is event sourcing with this package a good fit for a normal CRUD Laravel app?
- No. CQRS and event sourcing are an architectural commitment rather than a library you sprinkle into a conventional CRUD application, because append-only event schemas become a public contract and read models become eventually consistent. Adopt it only for a bounded context with genuine audit or replay requirements, such as a payments ledger, order lifecycle, or inventory movements. Isolate it to that context instead of making it the default application architecture.
- What alternatives exist if I do not want to depend on micro-module/broadway?
- Broadway is framework agnostic, so you can wire its CommandBus, EventBus, and EventStore into Laravel's container yourself in a service provider, which is essentially what this package does. Other PHP options include Spatie's event-sourcing package or Prooph, depending on whether you prefer explicit CQRS buses or an Eloquent-friendly aggregate model. Copying the glue code from this repository into your own application removes the single-maintainer risk entirely.