DBMS > Firebase Realtime Database vs. IBM Cloudant vs. IRONdb vs. SiteWhere

System Properties Comparison Firebase Realtime Database vs. IBM Cloudant vs. IRONdb vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Firebase Realtime Database  Xexclude from comparison	IBM Cloudant  Xexclude from comparison	IRONdb  Xexclude from comparison	SiteWhere  Xexclude from comparison
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	A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity	M2M integration platform for persisting/querying time series data
Primary database model	Document store	Document store	Time Series DBMS	Time Series DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 18.48 Rank #39   Overall #6   Document stores	Score 3.26 Rank #95   Overall #17   Document stores	Score 0.00 Rank #363   Overall #34   Time Series DBMS	Score 0.00 Rank #363   Overall #34   Time Series DBMS
Website	firebase.google.com/­products/­realtime-database	www.ibm.com/­cloud/­cloudant	www.circonus.com/­solutions/­time-series-database	sitewhere.io
Technical documentation	firebase.google.com/­docs/­database	cloud.ibm.com/­docs/­Cloudant	docs.circonus.com/­irondb	sitewhere.io/­docs/­2.1.0
Developer	Google acquired by Google 2014	IBM, Apache Software Foundation IBM acquired Cloudant in February 2014	Circonus LLC.	SiteWhere
Initial release	2012	2010	2017	2010
Current release			V0.10.20, January 2018
License Commercial or Open Source	commercial	commercial	commercial	Open Source Common Public Attribution License Version 1.0
Cloud-based only Only available as a cloud service	yes	yes	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language		Erlang	C and C++	Java
Server operating systems	hosted	hosted	Linux	Linux OS X Windows
Data scheme	schema-free	schema-free	schema-free	predefined scheme
Typing predefined data types such as float or date	yes	no	yes text, numeric, histograms	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.	no	no	no	no
Secondary indexes	yes	yes	no	no
SQL Support of SQL	no	no	SQL-like query language (Circonus Analytics Query Language: CAQL)	no
APIs and other access methods	Android iOS JavaScript API RESTful HTTP API	RESTful HTTP/JSON API	HTTP API	HTTP REST
Supported programming languages	Java JavaScript Objective-C	C# Java JavaScript Objective-C PHP Ruby	.Net C C++ Clojure Erlang Go Haskell Java JavaScript JavaScript (Node.js) Lisp Lua Perl PHP Python R Ruby Rust Scala
Server-side scripts Stored procedures	limited functionality with using 'rules'	View functions (Map-Reduce) in JavaScript	yes, in Lua
Triggers	Callbacks are triggered when data changes	yes	no
Partitioning methods Methods for storing different data on different nodes		Sharding	Automatic, metric affinity per node	Sharding based on HBase
Replication methods Methods for redundantly storing data on multiple nodes		Multi-source replication Source-replica replication	configurable replication factor, datacenter aware	selectable replication factor based on HBase
MapReduce Offers an API for user-defined Map/Reduce methods	no	yes	no	no
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 per node, eventual consistency across nodes	Immediate Consistency
Foreign keys Referential integrity	no	no	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	yes	no atomic operations within a document possible	no	no
Concurrency Support for concurrent manipulation of data	yes	yes Optimistic locking	yes	yes
Durability Support for making data persistent	yes	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.		no	no	no
User concepts Access control	yes, based on authentication and database rules	Access rights for users can be defined per database	no	Users with fine-grained authorization concept
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
	Firebase Realtime Database	IBM Cloudant	IRONdb	SiteWhere
DB-Engines blog posts	Cloud-based DBMS's popularity grows at high rates 12 December 2019, Paul Andlinger show all