DBMS > Firebase Realtime Database vs. JaguarDB vs. SQLite vs. SwayDB vs. WakandaDB

System Properties Comparison Firebase Realtime Database vs. JaguarDB vs. SQLite vs. SwayDB vs. WakandaDB

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.

Performant, highly scalable DBMS for AI and IoT applications

Widely used embeddable, in-process RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

Relational DBMS

Key-value store

Object oriented DBMS

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#384	Overall
	#60	Key-value stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

Technical documentation

firebase.google.com/docs/database

www.jaguardb.com/support.html

www.sqlite.org/docs.html

wakanda.github.io/doc

Developer

Google

acquired by Google 2014

DataJaguar, Inc.

Dwayne Richard Hipp

Simer Plaha

Wakanda SAS

Initial release

2012

2015

2000

2018

2012

Current release

3.3 July 2023

3.46.1 (13 August 2024), August 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Public Domain

Open Source

GNU Affero GPL V3.0

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

the server part. Clients available in other languages

Scala

C++, JavaScript

Server operating systems

hosted

Linux

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Go
Java
JavaScript (Node.js)
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

Java
Kotlin
Scala

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Atomic execution of operations

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

rights management via user accounts

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.