DBMS > Apache Phoenix vs. LMDB vs. RocksDB vs. Snowflake vs. Splunk

System Properties Comparison Apache Phoenix vs. LMDB vs. RocksDB vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Description

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

A high performant, light-weight, embedded key-value database library

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

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

phoenix.apache.org

www.symas.com/symas-embedded-database-lmdb

rocksdb.org

www.snowflake.com

www.splunk.com

Technical documentation

phoenix.apache.org

www.lmdb.tech/doc

github.com/facebook/rocksdb/wiki

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Symas

Facebook, Inc.

Snowflake Computing Inc.

Splunk Inc.

Initial release

2014

2011

2013

2014

2003

Current release

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

0.9.32, January 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

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

Linux

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

C++ API
Java API

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

C
C++
Go
Java
Perl
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.