DBMS > Firebase Realtime Database vs. GridGain vs. SQLite vs. TerminusDB

System Properties Comparison Firebase Realtime Database vs. GridGain vs. SQLite 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.

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

firebase.google.com/products/realtime-database

www.gridgain.com

www.sqlite.org

terminusdb.com

Technical documentation

firebase.google.com/docs/database

www.gridgain.com/docs/index.html

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Google

acquired by Google 2014

GridGain Systems, Inc.

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2012

2007

2000

2018

Current release

GridGain 8.5.1

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

Java, C++, .Net

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-92 is not fully supported

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.