DBMS > Apache IoTDB vs. Firebase Realtime Database vs. Google BigQuery vs. Microsoft Azure Synapse Analytics

System Properties Comparison Apache IoTDB vs. Firebase Realtime Database vs. Google BigQuery vs. Microsoft Azure Synapse Analytics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

Large scale data warehouse service with append-only tables

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Primary database model

Time Series DBMS

Document store

Relational DBMS

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

Score	1.19
Rank	#176	Overall
	#15	Time Series DBMS

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Website

iotdb.apache.org

firebase.google.com/products/realtime-database

cloud.google.com/bigquery

azure.microsoft.com/services/synapse-analytics

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

firebase.google.com/docs/database

cloud.google.com/bigquery/docs

docs.microsoft.com/azure/synapse-analytics

Developer

Apache Software Foundation

Google

acquired by Google 2014

Google

Microsoft

Initial release

2018

2012

2010

2016

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Data scheme

yes

schema-free

yes

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

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Java
JavaScript
Objective-C

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
PHP

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

user defined functions

in JavaScript

Transact SQL

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

yes

Since BigQuery is designed for querying data

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

yes, based on authentication and database rules

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

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.