DBMS > Ignite vs. InfinityDB vs. IRONdb vs. RocksDB

System Properties Comparison Ignite vs. InfinityDB vs. IRONdb vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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.

A Java embedded Key-Value Store which extends the Java Map interface

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

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	0.00
Rank	#378	Overall
	#57	Key-value stores

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

Website

ignite.apache.org

boilerbay.com

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

apacheignite.readme.io/docs

boilerbay.com/infinitydb/manual

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Boiler Bay Inc.

Circonus LLC.

Facebook, Inc.

Initial release

2015

2002

2017

2013

Current release

Apache Ignite 2.6

4.0

V0.10.20, January 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

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

Java

C and C++

C++

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

text, numeric, histograms

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

HTTP API

C++ API
Java API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

yes, in Lua

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

configurable replication factor, datacenter aware

yes

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

READ-COMMITTED or SERIALIZED

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

yes

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

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.