Weave Code
Message Bus Laravel Package
telephantast/message-bus
Telephantast Message Bus is a lightweight Laravel package for dispatching messages to dedicated handlers. It supports command and query handling with middleware, helping you build clean, decoupled, and testable PHP applications.
At a glance
Frequently asked questions about Message Bus
- What is telephantast/message-bus and what problem does it solve in Laravel?
- Telephantast Message Bus is a lightweight Laravel package for dispatching messages to dedicated handlers, with support for command and query handling plus middleware. It targets command/query separation or CQRS-lite patterns without hand-rolling a router. Conceptually it maps onto Laravel primitives such as the service container, queue dispatcher, and event system. The key question is whether it adds enough beyond Laravel's native Bus and Dispatcher to justify a third-party dependency.
- How do I install telephantast/message-bus with Composer?
- The evaluation indicates Composer-based installation with probable package auto-discovery and a publishable config, which keeps the footprint small. Before running composer require, confirm the canonical repository and exact package name because the repository field is listed as unknown. Audit the package's composer.json constraints against your locked dependency graph and test installation in a clean branch. Do not assume auto-discovery or config publishing behaves as expected until verified under Laravel's package manifest caching.
- Which Laravel and PHP versions does telephantast/message-bus support?
- The provided evaluation does not confirm a PHP or Laravel version support matrix, and it notes that low-star packages often have stale Composer constraints. You should audit composer.json constraints against your application's exact locked PHP and Laravel minor versions rather than assuming range compatibility. Run a timeboxed spike on your target versions before wider adoption. Also check whether the package declares a stability level such as dev, alpha, beta, or stable.
- How are command and query handlers registered in this Laravel message bus?
- The evaluation describes dedicated handlers and mentions handler discovery as a potential differentiator, but the exact registration mechanism is not confirmed. Message-bus packages can have implicit handler registration and middleware ordering, where mistakes appear as silent no-ops rather than loud errors. Your spike should dispatch one synchronous command and one query and confirm that missing or misordered handlers fail visibly. Verify the behavior with contract tests before relying on it in a bounded context.
- Does telephantast/message-bus support middleware, and how is middleware ordering handled?
- Middleware support is part of the package's stated purpose, but the evaluation does not document ordering semantics or composition details. Middleware ordering is a known risk area for message buses because implicit ordering can produce hard-to-diagnose dispatch bugs. Test middleware composition alongside Laravel's own global middleware in a small spike. Confirm that ordering is explicit, documented, and covered by tests before using it in critical flows.
- Can I dispatch queued or asynchronous messages with this package?
- The package dispatches messages and is positioned around command and query handling, and the evaluation flags async ergonomics as something to confirm rather than assume. Queued message serialization differs meaningfully across Redis, SQS, and database queue drivers, so test payload handling with your actual driver. Confirm that queued handlers, retries, and failures behave as expected. Treat queued dispatch as unproven until your spike includes at least one queued command end to end.
- How should I test a Laravel application that uses telephantast/message-bus?
- Put the bus behind a first-party interface owned by your application, such as an app-level CommandBus contract, and bind the package implementation to it. Then write contract tests for dispatch, middleware ordering, handler registration, and queued handlers. Because the repository is unknown, do not rely on package-level CI or coverage as your safety net. Pilot the bus in one bounded context with low transactional risk and expand only after those tests pass.
- How does telephantast/message-bus compare with Laravel's native bus, laravel-actions, or league/tactician?
- The evaluation says the distinction must be confirmed in a spike because a thin wrapper over Laravel's own Bus and Dispatcher is low value and easy to replace. Compare middleware pipeline behavior, handler discovery, async ergonomics, and how each option handles queued messages. If the package does not meaningfully differ from Laravel's native dispatcher or an established alternative, the third-party dependency may not be justified. Prefer the option with clearer documentation, maintenance, and compatibility with your Laravel version.
- Is telephantast/message-bus safe and maintained enough for production use?
- The main blocker is provenance: the repository field is unknown, which means no auditable source, CI signal, issue history, or security policy. At 19 stars the adoption base is effectively nil, which correlates with a single maintainer, thin test coverage, undocumented version support, and a higher chance of abandonment or breaking API churn before 1.0. For a package that receives commands and dispatches jobs, that is a supply-chain concern rather than a convenience concern. The MIT license is favorable because vendoring or forking is legally uncomplicated, but resolve source, tags, changelog, advisories, maintainer responsiveness, and any succession plan before adoption.
- What is a safe adoption and migration path for this message bus in an existing Laravel app?
- Adopt incrementally and reversibly by introducing the bus behind an application-owned interface and binding the package implementation to it. Pilot in one bounded context with low transactional risk, not in payments or authentication. Audit Composer constraints, auto-discovery under manifest caching, queue serialization with your driver, and middleware composition before expanding. This preserves the option to swap to Laravel's native dispatcher or another library without touching call sites.
Weaver
How can I help you explore Laravel packages today?