Service Bus Lite Laravel Package

Product Decisions This Supports

• Build vs. buy for command/query dispatching: Supports the decision to adopt a minimal, vendorable service bus instead of building a dispatcher from scratch or pulling in a heavyweight CQRS framework.
• Architecture direction: Reinforces command-query separation (CQRS-lite) as a roadmap item — routing writes through command handlers and reads through query handlers, decoupling controllers from domain logic.
• Refactor sequencing: Provides a low-risk mechanism to incrementally extract bloated controllers/services into discrete handlers without a framework migration.
• Extensibility bets: Its "lite" scope (a handler registry and dispatcher) means middleware, logging, and transactions are your build decisions — treat this as a pattern reference rather than a feature-complete backbone.
• Use cases it fits: Internal tools, small-to-medium APIs, plain-PHP services, or prototyping a bus abstraction where the transport is expected to change later.
• Not supported by this decision: Any roadmap item requiring community support, security patches, or ecosystem integrations — with 12 stars and 0 dependents, this is effectively an unaudited single-maintainer codebase.

When to Consider This Package

Consider it when:

• You are on plain PHP or a micro-framework and want a readable, MIT-licensed bus with no framework coupling.
• The team is already fluent in command/handler/query concepts and wants a thin starting point.
• You intend to fork or vendor-pin it and own the code — the implementation is small enough to audit in an afternoon.
• You want a learning/reference implementation of the pattern, or a spike to validate the architecture before committing.
• Your bus requirements are minimal: register handlers, dispatch a message, return a result.

Look elsewhere when:

• You are Laravel-native — use the framework's container and job/bus plumbing; this package ships no service provider, facade, or config.
• You need middleware pipelines, async transport, retries, or event sourcing — reach for League Tactician, Symfony Messenger, or Laravel's bus instead.
• You need maintenance guarantees, CVE response, or a support contract. Zero dependents and a low adoption score mean you are the maintainer the moment you install it.
• The decision is production-critical or long-lived; the bus-factor and abandonment risk outweigh the convenience.

How to Pitch It (Stakeholders)

To executives: A free, permissively licensed PHP component that helps structure code around a clean "one action, one handler" pattern. Cost is zero; the risk is adoption — it has a tiny user base and a single maintainer, so we should not treat it as a strategic dependency. Recommend it only for a scoped spike or internal tooling, with a fallback to a maintained alternative if the pattern proves out.

To engineering: It is a small, dependency-light command/query dispatcher — easy to read, easy to fork, and framework-agnostic. That is both its appeal and its limitation: no middleware, no async transport, no Laravel integration, and no community to lean on. If we adopt it, we vendor-pin it and accept ownership. If we want the same architecture with support behind it, we should compare against League Tactician or Symfony Messenger before committing.