DBMS > Firebase Realtime Database vs. InterSystems Caché vs. Oracle Berkeley DB vs. SQLite vs. WakandaDB

System Properties Comparison Firebase Realtime Database vs. InterSystems Caché vs. Oracle Berkeley DB vs. SQLite vs. WakandaDB

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed 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 multi-model DBMS and application server

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Object oriented DBMS

Secondary database models

Document store

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.intersystems.com/products/cache

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

www.sqlite.org

wakanda.github.io

Technical documentation

firebase.google.com/docs/database

docs.intersystems.com

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

www.sqlite.org/docs.html

wakanda.github.io/doc

Developer

Google

acquired by Google 2014

InterSystems

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Wakanda SAS

Initial release

2012

1997

1994

2000

2012

Current release

2018.1.4, May 2020

18.1.40, May 2020

3.46.0 (23 May 2024), May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Public Domain

Open Source

AGPLv3, extended 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, Java, C++ (depending on the Berkeley DB edition)

C++, JavaScript

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

depending on used data model

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Java

.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

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

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

Access rights for users, groups and roles

yes

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.