DBMS > Firebase Realtime Database vs. IBM Cloudant vs. Riak TS vs. SWC-DB

System Properties Comparison Firebase Realtime Database vs. IBM Cloudant vs. Riak TS vs. SWC-DB

Please select another system to include it in the comparison.

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.

Database as a Service offering based on Apache CouchDB

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A high performance, scalable Wide Column DBMS

Primary database model

Document store

Time Series DBMS

Wide column store

Secondary database models

Time Series DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

firebase.google.com/products/realtime-database

www.ibm.com/products/cloudant

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

firebase.google.com/docs/database

cloud.ibm.com/docs/Cloudant

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Google

acquired by Google 2014

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Open Source, formerly Basho Technologies

Alex Kashirin

Initial release

2012

2010

2015

2020

Current release

3.0.0, September 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

Erlang

C++

Server operating systems

hosted

Linux
OS X

Linux

Data scheme

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

restricted

SQL

Support of SQL

yes, limited

SQL-like query language

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

Supported programming languages

Java
JavaScript
Objective-C

C#
Java
JavaScript
Objective-C
PHP
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

Server-side scripts

Stored procedures

limited functionality with using 'rules'

View functions (Map-Reduce) in JavaScript

Erlang

Triggers

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

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

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

yes

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

yes, based on authentication and database rules

Access rights for users can be defined per database

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.

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 launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

Hundreds of Google Firebase websites might have leaked data online
19 March 2024, TechRadar

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page