DBMS > Amazon DocumentDB vs. KeyDB vs. MySQL vs. StarRocks

System Properties Comparison Amazon DocumentDB vs. KeyDB vs. MySQL vs. StarRocks

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used open source RDBMS

An open source, high-performance columnar analytical database that enables real-time, multi-dimensional, and highly concurrent data analytics

Forked from Apache Doris

Primary database model

Document store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.93
Rank	#198	Overall
	#93	Relational DBMS

Website

aws.amazon.com/documentdb

github.com/Snapchat/KeyDB
keydb.dev

www.mysql.com

www.starrocks.io

Technical documentation

aws.amazon.com/documentdb/resources

docs.keydb.dev

dev.mysql.com/doc

docs.starrocks.io/en-us/latest/introduction/StarRocks_intro

Developer

EQ Alpha Technology Ltd.

Oracle

since 2010, originally MySQL AB, then Sun

The Linux Foundation

since Feb 2023

Initial release

2019

1995

2020

Current release

8.4.0, April 2024

2.5.3, March 2023

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

C++, Java

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
MySQL protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Java

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by range and hash)

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

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

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

Users with fine-grained authorization concept

no user groups or roles

Role based access control and fine grained access rights

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.