DBMS > DolphinDB vs. EsgynDB vs. Google Cloud Datastore vs. RocksDB vs. RRDtool

System Properties Comparison DolphinDB vs. EsgynDB vs. Google Cloud Datastore vs. RocksDB vs. RRDtool

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.

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

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Secondary database models

Relational DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

www.dolphindb.com

www.esgyn.cn

cloud.google.com/datastore

rocksdb.org

oss.oetiker.ch/rrdtool

Technical documentation

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

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

DolphinDB, Inc

Esgyn

Google

Facebook, Inc.

Tobias Oetiker

Initial release

2018

2015

2008

2013

1999

Current release

v2.00.4, January 2022

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

commercial

free community version available

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux
Windows

Linux

hosted

Linux

HP-UX
Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

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

ADO.NET
JDBC
ODBC

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

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

C
C++
Go
Java
Perl
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

Java Stored Procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Multi-source replication using Paxos

yes

none

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.

none

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

yes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

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.