DBMS > Dragonfly vs. Hazelcast vs. RocksDB vs. Splunk

System Properties Comparison Dragonfly vs. Hazelcast vs. RocksDB vs. Splunk

Please select another system to include it in the comparison.

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 widely adopted in-memory data grid

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

Analytics Platform for Big Data

Primary database model

Key-value store

Search engine

Secondary database models

Document store

JSON support with IMDG 3.12

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

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

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

hazelcast.com

rocksdb.org

www.splunk.com

Technical documentation

www.dragonflydb.io/docs

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

DragonflyDB team and community contributors

Hazelcast

Facebook, Inc.

Splunk Inc.

Initial release

2023

2008

2013

2003

Current release

1.0, March 2023

5.3.6, November 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

Limited free edition and free developer edition 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++

Server operating systems

Linux

All OS with a Java VM

Linux

Linux
OS X
Solaris
Windows

Data scheme

scheme-free

schema-free

yes

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

HTTP REST

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
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

Event Listeners, Executor Services

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of command blocks and scripts

one or two-phase-commit; repeatable reads; read commited

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

User concepts

Access control

Password-based authentication

Role-based access control

Access rights for users and roles

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.