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

System Properties Comparison Firebase Realtime Database vs. Geode 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

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Document store

Key-value 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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Website

firebase.google.com/products/realtime-database

geode.apache.org

cloud.google.com/bigquery

azure.microsoft.com/services/synapse-analytics

Technical documentation

firebase.google.com/docs/database

geode.apache.org/docs

cloud.google.com/bigquery/docs

docs.microsoft.com/azure/synapse-analytics

Developer

Google

acquired by Google 2014

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Microsoft

Initial release

2012

2002

2010

2016

Current release

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

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 (OQL)

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
PHP

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

in JavaScript

Transact SQL

Triggers

Callbacks are triggered when data changes

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

yes, on a single node

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, based on authentication and database rules

Access rights per client and object definable

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.