Solr Laravel Package

Product Decisions This Supports

• Search and discovery roadmap for Ibexa DXP properties. This bundle is the Solr search-engine implementation for Ibexa DXP, so it directly supports decisions about site search quality, faceted navigation, filtering, sorting, and content discovery on Ibexa-based platforms. It is not a general-purpose Laravel search package and should not be evaluated as one.
• Build vs. buy for enterprise search. If the organization is already on Ibexa DXP, adopting this package is effectively “buy/inherit” rather than “build”: search integration ships as part of the DXP subscription, reducing custom integration and maintenance scope. If the organization is not on Ibexa DXP, this is a poor fit and a standalone search product should be evaluated instead.
• AI and vector-search readiness. Recent releases add dense-vector dynamic fields and an embedding visitor for search by embeddings. This supports roadmap decisions around semantic search, recommendation surfaces, and AI-assisted content discovery without building a separate vector-search integration immediately.
• Search experience differentiation. Supported capabilities include spell checking, aggregations, and multiple criterion visitors (content name, image, bookmark, user-enabled status, container). These map to product features such as “did you mean,” guided navigation, personalized saved-search/bookmark views, and richer content filtering.
• Platform upgrade planning. The package tracks Ibexa DXP major versions (v4.6.x and v5.0.x lines), PHP 8.3, Symfony 7.x, and Solr 9.8+. This informs decisions about when to schedule platform upgrades and whether search infrastructure must move in lockstep.
• Operational resilience decisions. Configurable Solr HTTP timeouts and retries, plus removal of Basic-auth credentials from error output, support reliability and security decisions for search-dependent customer experiences.
• Use-case prioritization. Best suited to content-heavy, high-traffic Ibexa DXP sites needing relevance tuning, faceting, and scalable search. Poorly suited to small brochure sites or non-Ibexa PHP applications where simpler search (database search, Laravel Scout, Meilisearch, Typesense, or Algolia) would deliver faster time-to-value.

When to Consider This Package

Consider it when:

• You are running or committed to Ibexa DXP and need the supported Solr search implementation rather than a custom search layer.
• Search is a first-class product surface: catalog/browse experiences, faceted filtering, relevance tuning, spell checking, or content discovery.
• You need search at scale and are prepared to operate Solr (or a managed Solr service) alongside the application.
• You want vendor-supported integration through an Ibexa DXP subscription rather than maintaining a bespoke Solr connector.
• You are evaluating vector/embedding-based search and want to stay within the Ibexa-supported path.
• Your platform standards already align with PHP 8.3 and Symfony 7.x, matching the v5 line.

Look elsewhere when:

• You are building on Laravel or a non-Ibexa PHP framework. This is an Ibexa DXP bundle, not a framework-agnostic Solr client; using it outside Ibexa DXP would create significant integration and support risk.
• You need a standalone, permissively licensed Solr integration. Licensing is dual: Ibexa Business Use License (requires a valid Ibexa DXP subscription) or GPLv2. Neither is a typical permissive OSS license for commercial embedding.
• Your search needs are simple — basic keyword search, low content volume, or no faceting — where database search or a lightweight hosted search service is cheaper and faster.
• You require strong independent community traction or ecosystem support. Public signals here are thin: very low stars, zero listed dependents, and releases are largely maintenance-level (“no significant changes” in several versions). The real support channel is Ibexa’s commercial relationship, not the open-source community.
• You are not prepared to operate Solr (indexing, schema/config management, capacity, upgrades). The package integrates with Solr; it does not remove Solr operational ownership.
• You need turnkey relevance/AI search without platform coupling. Dedicated search platforms may offer faster experimentation and broader framework support.

How to Pitch It (Stakeholders)

For executives: This is the supported Solr search engine for Ibexa DXP. For organizations already on Ibexa DXP, it provides enterprise-grade search — faceting, filtering, spell checking, and emerging vector/embedding capabilities — as part of the platform rather than as a bespoke build. That lowers delivery risk and total cost of ownership for content-heavy digital experiences. The main caveat is strategic: value is contingent on Ibexa DXP adoption, and licensing runs through the Ibexa subscription (or GPLv2). It is not a general-purpose or Laravel search package, and its public community footprint is minimal, so support expectations should be set through the vendor relationship.

For engineering: Treat this as an Ibexa DXP platform component, not a standalone library. It is a Symfony bundle implementing Solr-backed search for Ibexa, with an extensible visitor pattern for criteria and sort clauses, aggregation support, spell checking, and newer embedding/vector-field support. Current v5 targets PHP 8.3, Symfony 7.x, and Solr 9.8+. Operationally, plan for Solr lifecycle management, index configuration, and upgrade alignment with Ibexa DXP releases. Do not attempt to graft it into Laravel; if the stack is Laravel, evaluate Laravel-native search options instead. Because independent adoption signals are weak, pin versions, rely on vendor release notes and support channels, and validate integration behavior with the documented unit and Solr-backed integration test suites.