DBMS > Firebase Realtime Database vs. IRONdb vs. Microsoft Azure AI Search vs. SQLite vs. Transbase

System Properties Comparison Firebase Realtime Database vs. IRONdb vs. Microsoft Azure AI Search vs. SQLite vs. Transbase

Editorial information provided by DB-Engines

Name

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

Description

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

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

Search-as-a-service for web and mobile app development

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Vector DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

firebase.google.com/products/realtime-database

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

azure.microsoft.com/en-us/services/search

www.sqlite.org

www.transaction.de/en/products/transbase.html

Technical documentation

firebase.google.com/docs/database

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

learn.microsoft.com/en-us/azure/search

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

acquired by Google 2014

Circonus LLC.

Microsoft

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2012

2017

2015

2000

1987

Current release

V0.10.20, January 2018

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

free development license

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 and C++

Server operating systems

hosted

Linux

hosted

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

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

C#
Java
JavaScript
Python

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes, in Lua

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes, based on authentication and database rules

yes

using Azure authentication

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.