DBMS > Apache Phoenix vs. Firebird vs. Google BigQuery vs. Hazelcast

System Properties Comparison Apache Phoenix vs. Firebird vs. Google BigQuery vs. Hazelcast

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

Firebird is an open source RDBMS forked from Borland's InterBase

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Website

phoenix.apache.org

www.firebirdsql.org

cloud.google.com/bigquery

hazelcast.com

Technical documentation

phoenix.apache.org

www.firebirdsql.org/en/reference-manuals

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

Developer

Apache Software Foundation

Firebird Foundation

Google

Hazelcast

Initial release

2014

2000

As fork of Borland's InterBase

2010

2008

Current release

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

5.0.1, August 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Initial Developer's Public License

commercial

Open Source

Apache Version 2; commercial licenses available

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 and C++

Java

Server operating systems

Linux
Unix
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

All OS with a Java VM

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

user defined functions

PSQL

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Triggers

yes

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

Source-replica replication

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

Users with fine-grained authorization concept

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

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.