DBMS > LevelDB vs. RavenDB vs. RocksDB vs. TerminusDB vs. Trafodion

System Properties Comparison LevelDB vs. RavenDB vs. RocksDB vs. TerminusDB vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

github.com/google/leveldb

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

ravendb.net/docs

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

trafodion.apache.org/documentation.html

Developer

Google

Hibernating Rhinos

Facebook, Inc.

DataChemist Ltd.

Apache Software Foundation, originally developed by HP

Initial release

2011

2010

2013

2018

2014

Current release

1.23, February 2021

5.4, July 2022

8.11.4, April 2024

11.0.0, January 2023

2.3.0, February 2019

License

Commercial or Open Source

Open Source

BSD

Open Source

AGPL version 3, commercial license available

Open Source

BSD

Open Source

GPL V3

Open Source

Apache 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

C++

Prolog, Rust

C++, Java

Server operating systems

Illumos
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data 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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like query language (WOQL)

yes

APIs and other access methods

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Journaling Streams

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

in-memory journaling

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

Authorization levels configured per client per database

Role-based access control

fine grained access rights according to SQL-standard

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.