DBMS > Apache Phoenix vs. LMDB vs. RocksDB vs. TerminusDB

System Properties Comparison Apache Phoenix vs. LMDB vs. RocksDB vs. TerminusDB

Please select another system to include it in the comparison.

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)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

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

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

phoenix.apache.org

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

rocksdb.org

terminusdb.com

Technical documentation

phoenix.apache.org

www.lmdb.tech/doc

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation

Symas

Facebook, Inc.

DataChemist Ltd.

Initial release

2014

2011

2013

2018

Current release

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

0.9.32, January 2024

9.2.1, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
Unix
Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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
Python

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

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.