Bus Laravel Package
illuminate/bus
Illuminate Bus provides Laravel’s command bus for dispatching jobs, commands, and queued tasks. It supports sync and async dispatch, job chaining, batching, middleware-style pipelines, and robust integration with the queue system for background processing.
Technical Evaluation
Architecture fit: Tightly integrated with Laravel's core ecosystem (service container, queue system, event dispatcher), designed exclusively for monolithic Laravel applications. Not suitable for standalone PHP projects or microservices without significant abstraction layers.
Integration feasibility: Only feasible within Laravel projects (v13.0+); zero compatibility with non-Laravel stacks due to hard dependencies on illuminate/collections, contracts, and support. Attempting standalone usage would require resolving all transitive dependencies manually, leading to dependency conflicts.
Technical risk: High risk of over-engineering for trivial use cases (e.g., simple CRUD operations), dependency hell if extracted from Laravel, and potential misconfiguration of handler resolution or middleware pipelines. The package's "opportunity score" reflects Laravel's ecosystem traction, not standalone utility.
Key questions:
- Is the project built on Laravel? If not, why not use a framework-agnostic bus (e.g., Symfony Messenger)?
- Do the business requirements justify the command bus pattern's complexity (e.g., middleware for auditing, async processing, or domain-driven design)?
- Is the team experienced with Laravel's handler resolution conventions and queue workflows?
Integration Approach
Stack fit: Native compatibility with Laravel's existing infrastructure—queues (ShouldQueue interface), events (DispatchesEvents trait), and logging. Requires no additional configuration beyond standard Laravel setup (e.g., BusServiceProvider is auto-registered).
Migration path: For existing Laravel projects, adopt incrementally: start with synchronous dispatch (`
How can I help you explore Laravel packages today?