DBMS > DolphinDB vs. Drizzle vs. Google Cloud Datastore vs. Hawkular Metrics

System Properties Comparison DolphinDB vs. Drizzle vs. Google Cloud Datastore vs. Hawkular Metrics

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.

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Primary database model

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Website

www.dolphindb.com

cloud.google.com/datastore

www.hawkular.org

Technical documentation

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

cloud.google.com/datastore/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

Developer

DolphinDB, Inc

Drizzle project, originally started by Brian Aker

Google

Community supported by Red Hat

Initial release

2018

2008

2014

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

Open Source

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

Implementation language

C++

Java

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

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

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

HTTP REST

Supported programming languages

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

C
C++
Java
PHP

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

Go
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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
29 April 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

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

What Is Google Cloud Platform?
28 August 2023, Simplilearn

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Share this page