Making Postgres and Elasticsearch work together like it's 2020
ZomboDB brings powerful text-search and analytics features to Postgres by using Elasticsearch as an index type. Its comprehensive query language and SQL functions enable new and creative ways to query your relational data.
From a technical perspective, ZomboDB is a 100% native Postgres extension that implements Postgres' Index Access Method API. As a native Postgres index type, ZomboDB allows you to
CREATE INDEX ... USING zombodb on your existing Postgres tables. At that point, ZomboDB takes over and fully manages the remote Elasticsearch index and guarantees transactionally-correct text-search query results.
ZomboDB is fully compatible with all of Postgres' query plan types and most SQL commands such as
It doesn’t matter if you’re using an Elasticsearch cloud provider or managing your own cluster -- ZomboDB communicates with Elasticsearch via its RESTful APIs so you’re covered either way.
ZomboDB allows you to use the power and scalability of Elasticsearch directly from Postgres. You don’t have to manage transactions between Postgres and Elasticsearch, asynchronous indexing pipelines, complex reindexing processes, or multiple data-access code paths -- ZomboDB does it all for you.
- MVCC-correct text-search and aggregation results
- Managed and queried via standard SQL
- Works with current Elasticsearch releases (no plugins required)
- Query using
- Scoring and Highlighting Support
- Support for all Elasticsearch aggregations
- Automatic Elasticsearch Mapping Generation
- Ability to map custom domains
- Per-field custom mappings
json/jsonbautomatically mapped as dynamic nested objects
- Supports full set of Elasticsearch language analyzers
- Hot-Standby compatible
- Support for indexing & searching PostGIS
- Only one ZomboDB index per table
- ZomboDB indexes with predicates (ie, partial indexes) are not supported
CREATE INDEX CONCURRENTLYis not supported
These limitations may be addressed in future versions of ZomboDB.
Product | Version --- | --- Postgres | 10.x, 11.x Elasticsearch | 5.6.x, 6.x libcurl | >=7.28.0
- Google Group: email@example.com
- Twitter: @zombodb
- via Github Issues and Pull Requests
- https://www.zombodb.com/services/ or firstname.lastname@example.org for commercial support
The name is an homage to zombo.com and its long history of continuous self-affirmation.
This version of ZomboDB was graciously sponsored by Impira.
Historically, ZomboDB began in 2013 by Technology Concepts & Design, Inc as a closed-source effort to provide transaction safe text-search on top of Postgres tables. While Postgres' "tsearch" features are useful, they're not necessarily adequate for 200 column-wide tables with 100M rows, each containing large text content.
Initially designed on-top of Postgres' Foreign Data Wrapper API, ZomboDB quickly evolved into an index type so that queries are MVCC-safe and standard SQL can be used to query and manage indices.
Elasticsearch was chosen as the backing search index because of its horizontal scaling abilities, performance, and general ease of use.
ZomboDB was open-sourced in July 2015 and has since been used in numerous production systems of various sizes and complexity.