DBMS > Firebase Realtime Database vs. IBM Db2 vs. JaguarDB vs. Microsoft Azure Table Storage vs. Snowflake

System Properties Comparison Firebase Realtime Database vs. IBM Db2 vs. JaguarDB vs. Microsoft Azure Table Storage vs. Snowflake

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.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store
Vector DBMS

Wide column store

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.ibm.com/products/db2

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

Technical documentation

firebase.google.com/docs/database

www.ibm.com/docs/en/db2

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Google

acquired by Google 2014

IBM

DataJaguar, Inc.

Microsoft

Snowflake Computing Inc.

Initial release

2012

1983

host version

2015

2012

2014

Current release

12.1, October 2016

3.3 July 2023

License

Commercial or Open Source

commercial

free version is available

Open Source

GPL V3.0

commercial

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

C++

the server part. Clients available in other languages

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

hosted

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
ODBC

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

user defined functions

Triggers

Callbacks are triggered when data changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

optimistic locking

ACID

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.

User concepts

Access control

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

rights management via user accounts

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept, user roles and pluggable authentication

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.