DBMS > FatDB vs. Firebase Realtime Database vs. KairosDB vs. ObjectBox vs. Yanza

System Properties Comparison FatDB vs. Firebase Realtime Database vs. KairosDB vs. ObjectBox vs. Yanza

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Distributed Time Series DBMS based on Cassandra or H2

Extremely fast embedded database for small devices, IoT and Mobile

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Secondary database models

Time Series DBMS

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

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	1.22
Rank	#172	Overall
	#5	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

github.com/kairosdb/kairosdb

objectbox.io

yanza.com

Technical documentation

firebase.google.com/docs/database

kairosdb.github.io

docs.objectbox.io

Developer

FatCloud

Google

acquired by Google 2014

ObjectBox Limited

Yanza

Initial release

2012

2013

2017

2015

Current release

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

Windows

hosted

Linux
OS X
Windows

Android
iOS
Linux
macOS
Windows

Windows

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Android
iOS
JavaScript API
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

Proprietary native API

HTTP API

Supported programming languages

Java
JavaScript
Objective-C

Java
JavaScript

Node.js
PHP
Python

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

via applications

limited functionality with using 'rules'

Triggers

yes

via applications

Callbacks are triggered when data changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

online/offline synchronization between client and server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

Can implement custom security layer via applications

yes, based on authentication and database rules

simple password-based access control

yes

More information provided by the system vendor

News

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

Misconfigured Firebase instances leaked 19 million plaintext passwords
19 March 2024, BleepingComputer

provided by Google News

Expo: Real Time A/B Testing and Monitoring with Spark Streaming and Kafka at Walmart Labs
24 May 2019, InfoQ.com

provided by Google News

Industrial IoT (IIoT) edge solution for railway operators – a Kapsch ObjectBox Case Study
21 June 2019, 1E9

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

Share this page