DBMS > Firebase Realtime Database vs. Ignite vs. RocksDB vs. TerminusDB

System Properties Comparison Firebase Realtime Database vs. Ignite vs. RocksDB vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Document store

Key-value store
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	13.64
Rank	#39	Overall
	#6	Document stores

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

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

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

firebase.google.com/products/realtime-database

ignite.apache.org

rocksdb.org

terminusdb.com

Technical documentation

firebase.google.com/docs/database

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

Developer

Google

acquired by Google 2014

Apache Software Foundation

Facebook, Inc.

DataChemist Ltd.

Initial release

2012

2015

2013

2018

Current release

Apache Ignite 2.6

9.2.1, May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL V3

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

C++, Java, .Net

C++

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (WOQL)

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

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

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

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

yes

Triggers

Callbacks are triggered when data changes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Journaling Streams

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

yes, based on authentication and database rules

Security Hooks for custom implementations

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.