DBMS > Ignite vs. LevelDB vs. OpenTSDB vs. RocksDB vs. Tkrzw

System Properties Comparison Ignite vs. LevelDB vs. OpenTSDB vs. RocksDB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

Scalable Time Series DBMS based on HBase

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Key-value store
Relational DBMS

Key-value store

Time Series DBMS

Key-value store

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

ignite.apache.org

github.com/google/leveldb

opentsdb.net

rocksdb.org

dbmx.net/tkrzw

Technical documentation

apacheignite.readme.io/docs

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

opentsdb.net/docs/build/html/index.html

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Google

currently maintained by Yahoo and other contributors

Facebook, Inc.

Mikio Hirabayashi

Initial release

2015

2011

2013

2020

Current release

Apache Ignite 2.6

1.23, February 2021

8.11.4, April 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

LGPL

Open Source

BSD

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

C++, Java, .Net

C++

Java

C++

Server operating systems

Linux
OS X
Solaris
Windows

Illumos
Linux
OS X
Windows

Linux
Windows

Linux

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP API
Telnet API

C++ API
Java API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Erlang
Go
Java
Python
R
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

selectable replication factor

based on HBase

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

Security Hooks for custom implementations

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.