DBMS > Blueflood vs. RocksDB vs. Splunk vs. Tigris

System Properties Comparison Blueflood vs. RocksDB vs. Splunk vs. Tigris

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Analytics Platform for Big Data

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Time Series DBMS

Key-value store

Search engine

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.tigrisdata.com/docs

Developer

Rackspace

Facebook, Inc.

Splunk Inc.

Tigris Data, Inc.

Initial release

2013

2003

2022

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.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

Java

C++

Server operating systems

Linux
OS X

Linux

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

predefined scheme

schema-free

yes

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

SQL

Support of SQL

Splunk Search Processing Language for search commands

APIs and other access methods

HTTP REST

C++ API
Java API

HTTP REST

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

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.