DBMS > Apache Phoenix vs. Firebase Realtime Database vs. Google BigQuery vs. GridGain

System Properties Comparison Apache Phoenix vs. Firebase Realtime Database vs. Google BigQuery vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Relational DBMS

Document store

Relational DBMS

Key-value store
Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Website

phoenix.apache.org

firebase.google.com/products/realtime-database

cloud.google.com/bigquery

www.gridgain.com

Technical documentation

phoenix.apache.org

firebase.google.com/docs/database

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

Developer

Apache Software Foundation

Google

acquired by Google 2014

Google

GridGain Systems, Inc.

Initial release

2014

2012

2010

2007

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

GridGain 8.5.1

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

Java, C++, .Net

Server operating systems

Linux
Unix
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Java
JavaScript
Objective-C

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

Triggers

Callbacks are triggered when data changes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes, based on authentication and database rules

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

Google Cloud Identity & Access Management (IAM)

Security Hooks for custom implementations

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.