DBMS > Firebase Realtime Database vs. Google Cloud Bigtable vs. IBM Cloudant vs. Snowflake

System Properties Comparison Firebase Realtime Database vs. Google Cloud Bigtable vs. IBM Cloudant vs. Snowflake

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Database as a Service offering based on Apache CouchDB

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Key-value store
Wide column store

Document store

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/realtime-database

cloud.google.com/bigtable

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

firebase.google.com/docs/database

cloud.google.com/bigtable/docs

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Google

acquired by Google 2014

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2012

2015

2010

2014

License

Commercial or Open Source

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

Erlang

Server operating systems

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

Callbacks are triggered when data changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication
Source-replica replication

yes

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

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic single-row operations

atomic operations within a document possible

ACID

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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.