DBMS > Amazon DocumentDB vs. Amazon Redshift vs. Graph Engine vs. mSQL vs. TerarkDB

System Properties Comparison Amazon DocumentDB vs. Amazon Redshift vs. Graph Engine vs. mSQL vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

mSQL (Mini SQL) is a simple and lightweight 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

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Key-value store

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

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

Website

aws.amazon.com/documentdb

aws.amazon.com/redshift

www.graphengine.io

hughestech.com.au/products/msql

github.com/bytedance/terarkdb

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Microsoft

Hughes Technologies

ByteDance, originally Terark

Initial release

2019

2012

2010

1994

2016

Current release

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

free licenses can be provided

commercial

restricted open source version 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

.NET and C

C++

Server operating systems

hosted

.NET

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

RESTful HTTP API

JDBC
ODBC

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

informational only, not enforced by the system

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Access rights for users and roles

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.