DBMS > EsgynDB vs. Heroic vs. Oracle vs. TerarkDB vs. TerminusDB

System Properties Comparison EsgynDB vs. Heroic vs. Oracle vs. TerarkDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Widely used RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
RDF store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.esgyn.cn

github.com/spotify/heroic

www.oracle.com/database

github.com/bytedance/terarkdb

terminusdb.com

Technical documentation

spotify.github.io/heroic

docs.oracle.com/en/database

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

terminusdb.github.io/terminusdb/#

Developer

Esgyn

Spotify

Oracle

ByteDance, originally Terark

DataChemist Ltd.

Initial release

2015

2014

1980

2016

2018

Current release

23c, September 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

restricted open source version available

Open Source

GPL V3

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.

Implementation language

C++, Java

Java

C and C++

C++

Prolog, Rust

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

schema-free

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++
Java

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Multi-source replication
Source-replica replication

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

More information provided by the system vendor

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.