DBMS > DolphinDB vs. Drizzle vs. EsgynDB vs. Google Cloud Datastore

System Properties Comparison DolphinDB vs. Drizzle vs. EsgynDB vs. Google Cloud Datastore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Primary database model

Time Series DBMS

Relational DBMS

Document store

Secondary database models

Relational DBMS

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

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

www.dolphindb.com

www.esgyn.cn

cloud.google.com/datastore

Technical documentation

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

cloud.google.com/datastore/docs

Developer

DolphinDB, Inc

Drizzle project, originally started by Brian Aker

Esgyn

Google

Initial release

2018

2008

2015

2008

Current release

v2.00.4, January 2022

7.2.4, September 2012

License

Commercial or Open Source

commercial

free community version available

Open Source

GNU GPL

commercial

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

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

SQL-like query language (GQL)

APIs and other access methods

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

JDBC

ADO.NET
JDBC
ODBC

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

Supported programming languages

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

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Java Stored Procedures

using Google App Engine

Triggers

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication using Paxos

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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

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

Administrators, Users, Groups

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Best cloud storage of 2024
21 May 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Share this page