DBMS > Amazon DocumentDB vs. DolphinDB vs. Ingres vs. MySQL

System Properties Comparison Amazon DocumentDB vs. DolphinDB vs. Ingres vs. MySQL

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

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

Well established RDBMS

Widely used open source RDBMS

Primary database model

Document store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Relational DBMS

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	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/documentdb

www.dolphindb.com

www.actian.com/databases/ingres

www.mysql.com

Technical documentation

aws.amazon.com/documentdb/resources

docs.dolphindb.cn/en/help200/index.html

docs.actian.com/ingres

dev.mysql.com/doc

Developer

DolphinDB, Inc

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2019

2018

1974

originally developed at University Berkely in early 1970s

1995

Current release

v2.00.4, January 2022

11.2, May 2022

8.4.0, April 2024

License

Commercial or Open Source

commercial

free community version available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

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++

Server operating systems

hosted

Linux
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Ingres Replicator

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)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

Administrators, Users, Groups

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.