DBMS > EJDB vs. HEAVY.AI vs. OpenSearch vs. Postgres-XL

System Properties Comparison EJDB vs. HEAVY.AI vs. OpenSearch vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Secondary database models

Spatial DBMS

Vector DBMS

Document store
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

github.com/Softmotions/ejdb

github.com/heavyai/heavydb
www.heavy.ai

github.com/opensearch-project
opensearch.org

www.postgres-xl.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.heavy.ai

opensearch.org/docs/latest

www.postgres-xl.org/documentation

Developer

Softmotions

HEAVY.AI, Inc.

Amazon Web Services

Initial release

2012

2016

2021

2014

since 2012, originally named StormDB

Current release

5.10, January 2022

2.5.0, January 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache Version 2.0

Open Source

Mozilla public 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

C++ and CUDA

Java

Server operating systems

server-less

Linux

All OS with a Java VM

Linux
macOS

Data scheme

schema-free

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

in-process shared library

JDBC
ODBC
Thrift
Vega

Java API
RESTful HTTP/JSON API

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

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

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.