DBMS > Apache Doris vs. Dragonfly vs. Drizzle vs. EsgynDB vs. RocksDB

System Properties Comparison Apache Doris vs. Dragonfly vs. Drizzle vs. EsgynDB vs. RocksDB

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

An MPP-based analytics DBMS embracing the MySQL protocol

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

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

Primary database model

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

Score	0.57
Rank	#244	Overall
	#113	Relational DBMS

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

doris.apache.org
github.com/apache/doris

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.esgyn.cn

rocksdb.org

Technical documentation

github.com/apache/doris/wiki

www.dragonflydb.io/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation, originally contributed from Baidu

DragonflyDB team and community contributors

Drizzle project, originally started by Brian Aker

Esgyn

Facebook, Inc.

Initial release

2017

2023

2008

2015

2013

Current release

1.2.2, February 2023

1.0, March 2023

7.2.4, September 2012

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSL 1.1

Open Source

GNU GPL

commercial

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

C++, Java

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux

Data scheme

yes

scheme-free

yes

schema-free

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
MySQL client

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

Java

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Lua

Java Stored Procedures

Triggers

publish/subscribe channels provide some trigger functionality

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

fine grained access rights according to SQL-standard

Password-based authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.