DBMS > Amazon DocumentDB vs. Cubrid vs. MySQL vs. Warp 10

System Properties Comparison Amazon DocumentDB vs. Cubrid vs. MySQL vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Widely used open source RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/documentdb

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

www.mysql.com

www.warp10.io

Technical documentation

aws.amazon.com/documentdb/resources

cubrid.org/manuals

dev.mysql.com/doc

www.warp10.io/content/02_Getting_started

Developer

CUBRID Corporation, CUBRID Foundation

Oracle

since 2010, originally MySQL AB, then Sun

SenX

Initial release

2019

2008

1995

2015

Current release

11.0, January 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache License 2.0

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

C and C++

Java

Server operating systems

hosted

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.