DBMS > Firebase Realtime Database vs. IBM Db2 vs. KeyDB vs. Microsoft Azure Cosmos DB vs. Oracle Berkeley DB

System Properties Comparison Firebase Realtime Database vs. IBM Db2 vs. KeyDB vs. Microsoft Azure Cosmos DB vs. Oracle Berkeley DB

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Globally distributed, horizontally scalable, multi-model database service

Widely used in-process key-value store

Primary database model

Document store

Relational DBMS

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

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store
RDF store

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

with Db2 Spatial Extender

Spatial DBMS

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.70
Rank	#229	Overall
	#32	Key-value stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

firebase.google.com/products/realtime-database

www.ibm.com/products/db2

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/services/cosmos-db

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

firebase.google.com/docs/database

www.ibm.com/docs/en/db2

docs.keydb.dev

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Google

acquired by Google 2014

IBM

EQ Alpha Technology Ltd.

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

1983

host version

2019

2014

1994

Current release

12.1, October 2016

18.1.40, May 2020

License

Commercial or Open Source

commercial

free version is available

Open Source

BSD-3

commercial

Open Source

commercial license available

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

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

JSON types

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

only with the Berkeley DB XML edition

Secondary indexes

yes

by using the Redis Search module

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Proprietary protocol

RESP - REdis Serialization Protoco

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Java
JavaScript
Objective-C

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Lua

JavaScript

Triggers

Callbacks are triggered when data changes

yes

JavaScript

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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
Strong eventual consistency with CRDTs

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

simple password-based access control and ACL

Access rights can be defined down to the item level

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.