Official PHP client for Elasticsearch, providing a comprehensive interface to interact with Elasticsearch clusters from PHP applications.
Elasticsearch PHP client is the official PHP library for interacting with Elasticsearch, the distributed search and analytics engine. It provides a comprehensive interface to index, search, update, and delete documents, enabling PHP applications to leverage powerful full-text search capabilities. The client supports all Elasticsearch APIs and is designed for seamless integration with Elasticsearch clusters.
PHP developers building applications that require advanced search functionality, data analytics, or real-time data indexing with Elasticsearch.
Developers choose this client because it's the officially supported solution from Elastic, ensuring reliability, compatibility, and full API coverage. Its adherence to PSR standards and built-in serverless support make it a robust and future-proof choice for Elasticsearch integration.
Official PHP client for Elasticsearch.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
As the officially supported client, it covers 500+ Elasticsearch endpoints, ensuring no API gaps and reliable integration directly from Elastic.
Released alongside Elasticsearch server versions, it guarantees compatibility and reduces breakage, as noted in the versioning table for 8.x and 9.x branches.
Built with PSR-7 and PSR-18 compliance, making it interoperable with other PHP libraries and frameworks for HTTP messaging and client communications.
Supports mocking using any PSR-18 HTTP client, such as php-http/mock-client, simplifying unit and integration tests without needing a live Elasticsearch instance.
Includes automatic detection for Elasticsearch serverless deployments, with merged functionality from the deprecated elastic/elasticsearch-serverless client, as highlighted in the 9.0.0 changes.
Version 9.0 introduced backward incompatible changes, such as removing Guzzle dependency and merging serverless features, which can disrupt existing projects, as detailed in the BREAKING_CHANGES file.
Tightly coupled with Elasticsearch's ecosystem; switching to another search engine requires rewriting integration code, limiting flexibility for multi-backend strategies.
Requires deep understanding of Elasticsearch's APIs and concepts, adding learning curve and setup time compared to simpler, drop-in search solutions for basic needs.
Strict version alignment means clients must upgrade in sync with Elasticsearch server, potentially forcing frequent updates and testing cycles to maintain compatibility.