DBMS > EJDB vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL

System Properties Comparison EJDB vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL

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

Globally distributed, horizontally scalable, multi-model database service

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Document store

Graph DBMS
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Website

github.com/Softmotions/ejdb

www.graphengine.io

azure.microsoft.com/services/cosmos-db

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

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

www.graphengine.io/docs/manual

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Softmotions

Microsoft

Oracle

Initial release

2012

2010

2014

2011

Current release

24.1, May 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

MIT License

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

Java

Server operating systems

server-less

.NET

hosted

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

optional

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

in-process shared library

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

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

C#
C++
F#
Visual Basic

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

Multi-item ACID transactions with snapshot isolation within a partition

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

Access rights can be defined down to the item level

Access rights for users and roles

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.