DBMS > Apache Phoenix vs. BoltDB vs. CockroachDB vs. RocksDB vs. Splunk

System Properties Comparison Apache Phoenix vs. BoltDB vs. CockroachDB vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Analytics Platform for Big Data

Primary database model

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

phoenix.apache.org

github.com/boltdb/bolt

www.cockroachlabs.com

rocksdb.org

www.splunk.com

Technical documentation

phoenix.apache.org

www.cockroachlabs.com/docs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Cockroach Labs

Facebook, Inc.

Splunk Inc.

Initial release

2014

2013

2015

2013

2003

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

24.1.0, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

Apache 2.0, commercial license 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

Java

C++

Server operating systems

Linux
Unix
Windows

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

dynamic schema

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

yes

yes, wire compatible with PostgreSQL

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

C++ API
Java API

HTTP REST

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication using RAFT

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.