DBMS > OpenSearch vs. PostGIS vs. TimescaleDB vs. XTDB

System Properties Comparison OpenSearch vs. PostGIS vs. TimescaleDB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Spatial extension of PostgreSQL

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Vector DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/opensearch-project
opensearch.org

postgis.net

www.timescale.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

opensearch.org/docs/latest

postgis.net/documentation

docs.timescale.com

www.xtdb.com/docs

Developer

Amazon Web Services

Timescale

Juxt Ltd.

Initial release

2021

2005

2017

2019

Current release

2.5.0, January 2023

3.4.2, February 2024

2.13.0, November 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL v2.0

Open Source

Apache 2.0

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

Clojure

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

schema-free

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

yes, extensible-data-notation format

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

full PostgreSQL SQL syntax

limited SQL, making use of Apache Calcite

APIs and other access methods

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST
JDBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

Source-replica replication with hot standby and reads on replicas

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.