DBMS > Dragonfly vs. Elasticsearch vs. RocksDB vs. Spark SQL vs. TerarkDB

System Properties Comparison Dragonfly vs. Elasticsearch vs. RocksDB vs. Spark SQL vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

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

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

www.elastic.co/elasticsearch

rocksdb.org

spark.apache.org/sql

github.com/bytedance/terarkdb

Technical documentation

www.dragonflydb.io/docs

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

DragonflyDB team and community contributors

Elastic

Facebook, Inc.

Apache Software Foundation

ByteDance, originally Terark

Initial release

2023

2010

2013

2014

2016

Current release

1.0, March 2023

8.6, January 2023

8.11.4, April 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Elastic License

Open Source

BSD

Open Source

Apache 2.0

commercial

restricted open source version available

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

C++

Java

C++

Scala

C++

Server operating systems

Linux

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

scheme-free

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

Java API
RESTful HTTP/JSON API

C++ API
Java API

JDBC
ODBC

C++ API
Java API

Supported programming languages

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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Java
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

Lua

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of command blocks and scripts

yes

Concurrency

Support for concurrent manipulation of data

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

Memcached and Redis integration

yes

User concepts

Access control

Password-based authentication

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.