DBMS > EsgynDB vs. RocksDB vs. Solr vs. Splunk vs. SwayDB

System Properties Comparison EsgynDB vs. RocksDB vs. Solr vs. Splunk vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A widely used distributed, scalable search engine based on Apache Lucene

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

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	86.45
Rank	#14	Overall
	#2	Search engines

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

Website

Technical documentation

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

docs.splunk.com/Documentation/Splunk

Developer

Esgyn

Facebook, Inc.

Apache Software Foundation

Splunk Inc.

Simer Plaha

Initial release

2015

2013

2006

2003

2018

Current release

8.11.4, April 2024

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Apache Version 2

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

C++

Java

Scala

Server operating systems

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

Java API
RESTful HTTP/JSON API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

Java plugins

yes

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

ACID

yes

optimistic locking

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

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

yes

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.