DBMS > Firebase Realtime Database vs. KairosDB vs. PouchDB vs. RocksDB vs. SQream DB

System Properties Comparison Firebase Realtime Database vs. KairosDB vs. PouchDB vs. RocksDB vs. SQream 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.

Distributed Time Series DBMS based on Cassandra or H2

JavaScript DBMS with an API inspired by CouchDB

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

firebase.google.com/products/realtime-database

github.com/kairosdb/kairosdb

pouchdb.com

rocksdb.org

sqream.com

Technical documentation

firebase.google.com/docs/database

kairosdb.github.io

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.sqream.com

Developer

Google

acquired by Google 2014

Apache Software Foundation

Facebook, Inc.

SQream Technologies

Initial release

2012

2013

2012

2013

2017

Current release

1.2.2, November 2018

7.1.1, June 2019

9.2.1, May 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

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

Java

JavaScript

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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.

Secondary indexes

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

.Net
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

Java
JavaScript

Node.js
PHP
Python

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

View functions in JavaScript

user defined functions in Python

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

by using IndexedDB, WebSQL or LevelDB as backend

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

simple password-based access control

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.