DBMS > DolphinDB vs. Dolt vs. Google Cloud Datastore vs. MySQL

System Properties Comparison DolphinDB vs. Dolt vs. Google Cloud Datastore vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

A MySQL compatible DBMS with Git-like versioning of data and schema

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Relational DBMS

Document store

Document store
Spatial DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

www.dolphindb.com

github.com/dolthub/dolt
www.dolthub.com

cloud.google.com/datastore

www.mysql.com

Technical documentation

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

docs.dolthub.com

cloud.google.com/datastore/docs

dev.mysql.com/doc

Developer

DolphinDB, Inc

DoltHub Inc

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2018

2008

1995

Current release

v2.00.4, January 2022

8.4.0, April 2024

License

Commercial or Open Source

commercial

free community version available

Open Source

Apache Version 2.0

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

Linux
Windows

Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language

yes

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

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

CLI Client
HTTP REST

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
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

yes

currently in alpha release

using Google App Engine

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

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

Administrators, Users, Groups

Only one user is configurable, and must be specified in the config file at startup

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.