- What is lmc/cqrs-http used for in Laravel?
- It is a thin transport helper that bridges the HTTP layer with CQRS by mapping incoming requests to command and query objects. It handles dispatching, validation plumbing, and response transformation so controllers can stay thin. It fits Laravel applications that already separate commands and queries and need shared HTTP-bound contracts, not conventional CRUD monoliths.
- How do I install lmc/cqrs-http?
- Install it with Composer using composer require lmc/cqrs-http. The 3.0.0 release requires PHP 8.1 or newer, so confirm your runtime before adopting it. Composer installation and MIT licensing are straightforward, but expect to add your own Laravel service provider, bindings, and configuration.
- Does lmc/cqrs-http support Laravel package auto-discovery?
- There is no visible Laravel ecosystem adoption, so do not assume auto-discovery or ready-made Laravel documentation. Plan to register the service provider, container bindings, configuration, and HTTP client adaptation manually. Verify the package's Composer metadata before relying on Laravel-specific integration behavior.
- What PHP and Laravel versions does lmc/cqrs-http 3.0.0 require?
- The 3.0.0 line requires PHP 8.1 or newer, which blocks teams still on PHP 8.0 without a runtime upgrade. The available context does not confirm exact Laravel version constraints beyond likely custom integration work. Check the package's composer.json for its full dependency and framework constraints.
- Is lmc/cqrs-http a full CQRS framework?
- No, it is a thin CQRS-over-HTTP transport helper rather than a complete CQRS framework. It does not replace your command bus, query bus, persistence, events, queues, or authorization design. Adopt it only when it removes real boilerplate around HTTP command and query contracts.
- What changed in lmc/cqrs-http 3.0.0?
- The 3.0.0 release is described as a breaking change that uses new language features and changes method signatures. No migration guide, changelog detail, or deprecation path is visible in the provided context. If you fork or adopt it, base that work on the 3.0.0 tag rather than backporting from 2.x.
- Can I use lmc/cqrs-http in production?
- Treat it as high risk: it has very low visible adoption, 1 GitHub star, 0 dependents, and 3.0.0 from April 2022 is still the newest release. Risks include abandonment, PHP and Laravel incompatibility, undocumented coupling, and unknown test coverage. Use it only for a time-boxed spike or isolated flow behind an internal abstraction, not as a foundational dependency.
- How should I integrate lmc/cqrs-http with Laravel?
- Wrap it behind internal interfaces such as HttpCommandBus and HttpQueryBus so application code does not depend directly on LMC classes. Keep Laravel-native validation, authorization, events, queues, and persistence in your application, and add custom container bindings, configuration, authentication propagation, and error mapping. This isolation matters because the 3.0.0 method-signature changes show the kind of churn you want to contain.
- Does lmc/cqrs-http handle validation and response formatting?
- The package advertises automatic request validation, payload mapping to command objects, and pluggable response handlers for JSON and custom formats. Verify how it handles serialization, authentication, retries, idempotency, and correlation IDs in your integration. Keep critical validation and response policy in Laravel or your own internal layer if the package's behavior is undocumented.
- What are alternatives to lmc/cqrs-http?
- A lower-risk alternative is Laravel's HTTP client plus a small internal command and query contract with native validation, authorization, events, and queues. That avoids depending on a low-adoption package whose newest release is from 2022. If you need CQRS conventions, define them internally or evaluate actively maintained packages with clear Laravel support.