DBMS > Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. Trafodion vs. Warp 10

System Properties Comparison Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. Trafodion vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

Transactional SQL-on-Hadoop DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

firebase.google.com/products/realtime-database

azure.microsoft.com/services/cosmos-db

trafodion.apache.org

www.warp10.io

Technical documentation

firebase.google.com/docs/database

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

www.warp10.io/content/02_Getting_started

Developer

Google

acquired by Google 2014

Microsoft

Apache Software Foundation, originally developed by HP

SenX

Initial release

2012

2014

2015

Current release

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.0

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

C++, Java

Java

Server operating systems

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
JavaScript
Objective-C

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

limited functionality with using 'rules'

JavaScript

Java Stored Procedures

yes

WarpScript

Triggers

Callbacks are triggered when data changes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, via HBase

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

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.

yes

User concepts

Access control

yes, based on authentication and database rules

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.