DBMS > EJDB vs. Graph Engine vs. Heroic vs. OpenSearch

System Properties Comparison EJDB vs. Graph Engine vs. Heroic vs. OpenSearch

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Document store

Graph DBMS
Key-value store

Time Series DBMS

Search engine

Secondary database models

Vector DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

github.com/Softmotions/ejdb

www.graphengine.io

github.com/spotify/heroic

github.com/opensearch-project
opensearch.org

Technical documentation

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

www.graphengine.io/docs/manual

spotify.github.io/heroic

opensearch.org/docs/latest

Developer

Softmotions

Microsoft

Spotify

Amazon Web Services

Initial release

2012

2010

2014

2021

Current release

2.5.0, January 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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

.NET and C

Java

Server operating systems

server-less

.NET

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

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

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.

Secondary indexes

yes

via Elasticsearch

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

in-process shared library

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

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

C#
C++
F#
Visual Basic

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.