DBMS > Apache Phoenix vs. EsgynDB vs. Google Cloud Bigtable vs. H2

System Properties Comparison Apache Phoenix vs. EsgynDB vs. Google Cloud Bigtable vs. H2

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Website

phoenix.apache.org

www.esgyn.cn

cloud.google.com/bigtable

www.h2database.com

Technical documentation

phoenix.apache.org

cloud.google.com/bigtable/docs

www.h2database.com/html/main.html

Developer

Apache Software Foundation

Esgyn

Google

Thomas Mueller

Initial release

2014

2015

2005

Current release

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

2.2.220, July 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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++, Java

Java

Server operating systems

Linux
Unix
Windows

Linux

hosted

All OS with a Java VM

Data scheme

yes

late-bound, schema-on-read capabilities

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

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

Java

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Java Stored Procedures and User-Defined Functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

With clustering: 2 database servers on different computers operate on identical copies of a database

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 (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

show all

Recent citations in the news

Supercharge SQL on Your Data in Apache HBase with Apache Phoenix | Amazon Web Services
2 June 2016, AWS Blog

Bridge the SQL-NoSQL gap with Apache Phoenix
4 February 2016, InfoWorld

Apache Calcite, FreeMarker, Gora, Phoenix, and Solr updated
27 March 2017, SDTimes.com

Azure HDInsight Analytics Platform Now Supports Apache Hadoop 3.0
18 April 2019, eWeek

Amazon EMR 4.7.0 – Apache Tez & Phoenix, Updates to Existing Apps | Amazon Web Services
2 June 2016, AWS Blog

provided by Google News

Google expands BigQuery with Gemini, brings vector support to cloud databases
29 February 2024, VentureBeat

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

provided by Google News

Share this page