Cqrs Solr Laravel Package

Product Decisions This Supports

• Search feature feasibility: Use it to evaluate Solr-backed search use cases such as catalog search, faceted filtering, saved searches, admin reindexing, and read-heavy query experiences in a PHP/Laravel stack.
• Build vs. buy vs. borrow: Treat the package as a low-cost reference implementation for CQRS-style Solr commands and queries, not as a strategic platform dependency. It can reduce early boilerplate if the team already uses Solr and command/query separation.
• Roadmap sequencing: Supports a timeboxed spike to validate Solr fit before committing roadmap capacity to a custom search abstraction. Low stars, zero dependents, a 2022 last release, and a breaking 3.0.0 with no follow-on releases mean adoption should be scoped as an experiment or internal utility, not a core product bet.
• Architecture standardization: Informs whether to standardize Solr access behind an internal interface, adopt a thin vendor package, or build a maintained in-house layer. Given the maturity and maintenance signals, the safer product decision is usually to wrap or fork rather than couple directly.
• Use-case prioritization: Best suited to teams with existing Solr expertise and a clear CQRS need. It is less relevant for teams seeking a managed search product, advanced relevance tooling, or an actively maintained search SDK.

When to Consider This Package

Consider it when:

• The product already uses Solr and PHP/Laravel, and the team wants base implementations for Solr queries and commands.
• The architecture already embraces CQRS or command/query separation.
• The runtime is PHP 8.1+ — 3.0.0 raises the floor and deliberately breaks method signatures to use newer language features, so older PHP 8.0/7.x environments cannot consume the current major version.
• The need is an internal accelerator, proof of concept, or reference pattern rather than a long-term vendor dependency.
• The team is willing to fork, wrap, and maintain the code under its MIT license.
• The scope is low-risk and timeboxed, with clear exit criteria and no hard production SLA dependency.

Look elsewhere when:

• You need an actively maintained, widely adopted search package with a strong support ecosystem.
• You are pinned to PHP 8.0 or earlier, or cannot absorb a breaking major-version upgrade in a dependency you did not author.
• You require managed search, Elasticsearch/OpenSearch compatibility, advanced relevance tuning, analytics, or multi-tenant search.
• The team lacks Solr operational expertise or cannot absorb maintenance risk.
• Search is a core, differentiating product capability where reliability, observability, and long-term ownership matter.
• You are not using CQRS or Solr and would be adopting the package only for speculative future needs.

How to Pitch It (Stakeholders)

Executive summary: lmc/cqrs-solr is a small MIT-licensed PHP package that may accelerate Solr query/command plumbing for a CQRS-based search feature. It is not a strategic dependency: very low adoption, no dependents, and no release since 2022. The latest major (3.0.0) is itself from 2022 and is a breaking release that requires PHP 8.1 and changes method signatures — a signal of thin maintenance rather than active investment. I recommend using it only as a timeboxed spike or reference implementation, wrapping it behind an internal interface, and avoiding direct coupling to core roadmap commitments.

For engineering: It may reduce boilerplate for Solr-backed commands and queries if the stack already matches. Treat it as a forkable starting point, not a maintained platform component. Note that 3.0.0 is a hard compatibility gate — PHP 8.1+ only, with deliberate BC breaks and no 3.x maintenance releases since — so budget for owning upgrades, validating failure modes, and carrying the code in-house.

For product: It can help de-risk early Solr search experiments, but it should not drive the search roadmap. The product decision is whether Solr plus CQRS is the right search architecture; this package is at most a tactical accelerator, and the stale, breaking-only release history reinforces that framing.