DBMS > EJDB vs. HugeGraph vs. Microsoft Azure Cosmos DB vs. SAP HANA

System Properties Comparison EJDB vs. HugeGraph vs. Microsoft Azure Cosmos DB vs. SAP HANA

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 fast-speed and highly-scalable Graph DBMS

Globally distributed, horizontally scalable, multi-model database service

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/Softmotions/ejdb

github.com/hugegraph
hugegraph.apache.org

azure.microsoft.com/services/cosmos-db

www.sap.com/products/hana.html

Technical documentation

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

hugegraph.apache.org/docs

learn.microsoft.com/azure/cosmos-db

help.sap.com/hana

Developer

Softmotions

Baidu

Microsoft

SAP

Initial release

2012

2018

2014

2010

Current release

0.9

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

server-less

Linux
macOS
Unix

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

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

also supports composite index and range index

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

in-process shared library

Java API
RESTful HTTP API
TinkerPop Gremlin

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

JDBC
ODBC

Supported programming languages

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

Groovy
Java
Python

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

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

JavaScript

SQLScript, R

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

edges in graph

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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

Users, roles and permissions

Access rights can be defined down to the item level

yes

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.