DBMS > Dgraph vs. RocksDB vs. Sphinx vs. Splunk vs. SwayDB

System Properties Comparison Dgraph vs. RocksDB vs. Sphinx vs. Splunk vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Open source search engine for searching in data from different sources, e.g. relational databases

Analytics Platform for Big Data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

Technical documentation

dgraph.io/docs

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

docs.splunk.com/Documentation/Splunk

Developer

Dgraph Labs, Inc.

Facebook, Inc.

Sphinx Technologies Inc.

Splunk Inc.

Simer Plaha

Initial release

2016

2013

2001

2003

2018

Current release

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL version 2, commercial licence available

commercial

Limited free edition and free developer edition available

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

Splunk Search Processing Language for search commands

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

C++ API
Java API

Proprietary protocol

HTTP REST

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java
JavaScript
PHP
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

none

Multi-source replication

none

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

Transaction concepts

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

ACID

yes

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

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Planned for future releases

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.