- What is gmizera/service-bus-lite used for in a Laravel application?
- It is a lightweight service bus for Laravel that routes commands and queries to their handlers through a simple, explicit API. Instead of letting controllers call domain logic directly, you register handlers and dispatch messages, which keeps application boundaries clean. It is aimed at teams that want command/query separation without pulling in a full-blown framework or extra infrastructure.
- How do I install gmizera/service-bus-lite with Composer?
- Install it like any Laravel package with composer require gmizera/service-bus-lite. If the package ships a service provider, register it in your application or let Laravel package discovery handle it. Check the package README for any publishable config or required setup steps after installation.
- How do I register handlers and dispatch a command with this service bus?
- You map each command or query class to its handler using the package's registration API, then dispatch the message through the bus. The handler receives the message object and contains the actual logic, so your controller stays thin. Consult the README for the exact registration and dispatch method names, since the API is kept explicit and minimal by design.
- What is the difference between commands and queries in this service bus?
- Commands represent actions that change state, while queries represent read operations that return data. Both are routed to handlers, but keeping them separate makes intent clear and helps prevent read logic from leaking into write paths. This is the command/query separation pattern the package is built around.
- Does the service bus resolve handlers through Laravel's service container?
- Because it is a Laravel package, handlers are designed to work with the framework's container, so you can type-hint dependencies in a handler's constructor. Check the README for the exact resolution behavior. You can still register your own bindings in a service provider if you need custom wiring.
- Do I need Redis, queues, or other infrastructure to use gmizera/service-bus-lite?
- The package is designed to avoid extra infrastructure and full-blown framework dependencies, routing messages to handlers in-process rather than acting as a distributed broker. That makes it a good fit for apps that just need clean boundaries between controllers and domain logic. If you later need asynchronous processing, you can layer Laravel's queue system on top yourself.
- Which Laravel and PHP versions does gmizera/service-bus-lite support?
- The package targets Laravel applications, but the exact version constraints live in its composer.json and on Packagist. Check those requirements before adding it to an older or newer project. The available package information does not pin specific Laravel or PHP versions.
- How does it compare to a full command bus framework or queue-based dispatching?
- It deliberately does less: you get explicit handler registration and message dispatch without a large framework or message broker setup. That makes it a good fit for small to mid-sized apps that want clean boundaries with minimal ceremony. If you need middleware pipelines, async transport, or distributed messaging, evaluate whether a fuller bus or Laravel's queue system fits better.
- How should I test handlers and dispatched commands with this package?
- Handlers are ordinary classes, so the simplest approach is to instantiate them with mocked dependencies and assert their behavior directly. For controllers, assert that the expected command or query object is dispatched to the bus, using a fake or mock if the package provides one. Check the README for any built-in testing helpers before writing your own.
- Is gmizera/service-bus-lite actively maintained and safe to use in production?
- Since repository and release details are not listed here, verify release activity, issue responses, and open pull requests on the package's GitHub and Packagist pages before adopting it. Its scope is small and dependency-light, which keeps the production surface area low. Pin a specific version in composer.json and skim the source, since the codebase is intentionally small.