DBMS > EJDB vs. Graph Engine vs. Oracle vs. TerarkDB

System Properties Comparison EJDB vs. Graph Engine vs. Oracle vs. TerarkDB

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

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

Primary database model

Document store

Graph DBMS
Key-value store

Relational DBMS

Key-value store

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

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	1236.29
Rank	#1	Overall
	#1	Relational DBMS

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

Website

github.com/Softmotions/ejdb

www.graphengine.io

www.oracle.com/database

github.com/bytedance/terarkdb

Technical documentation

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

www.graphengine.io/docs/manual

docs.oracle.com/en/database

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Softmotions

Microsoft

Oracle

ByteDance, originally Terark

Initial release

2012

2010

1980

2016

Current release

23c, September 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

MIT License

commercial

restricted free version is available

commercial

restricted open source version available

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

.NET and C

C and C++

C++

Server operating systems

server-less

.NET

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

in-process shared library

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

C++ API
Java API

Supported programming languages

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

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

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

isolation level can be parameterized

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

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.