DBMS > Amazon DynamoDB vs. Cubrid vs. EJDB vs. JanusGraph vs. Microsoft SQL Server

System Properties Comparison Amazon DynamoDB vs. Cubrid vs. EJDB vs. JanusGraph vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Microsofts flagship relational DBMS

Primary database model

Document store
Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

aws.amazon.com/dynamodb

cubrid.com (korean)
cubrid.org (english)

github.com/Softmotions/ejdb

janusgraph.org

www.microsoft.com/en-us/sql-server

Technical documentation

docs.aws.amazon.com/dynamodb

cubrid.org/manuals

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

docs.janusgraph.org

learn.microsoft.com/en-US/sql/sql-server

Developer

Amazon

CUBRID Corporation, CUBRID Foundation

Softmotions

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Initial release

2012

2008

2012

2017

1989

Current release

11.0, January 2021

0.6.3, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

GPLv2

Open Source

Apache 2.0

commercial

restricted free version is available

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

C, C++, Java

Java

C++

Server operating systems

hosted

Linux
Windows

server-less

Linux
OS X
Unix
Windows

Linux
Windows

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

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

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

in-process shared library

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Clojure
Java
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

yes

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

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.