DBMS > Apache Phoenix vs. EsgynDB vs. Google Cloud Bigtable vs. Quasardb vs. SAP HANA

System Properties Comparison Apache Phoenix vs. EsgynDB vs. Google Cloud Bigtable vs. Quasardb vs. SAP HANA

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.

Distributed, high-performance timeseries database

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

phoenix.apache.org

www.esgyn.cn

cloud.google.com/bigtable

quasar.ai

www.sap.com/products/hana.html

Technical documentation

phoenix.apache.org

cloud.google.com/bigtable/docs

doc.quasar.ai/master

help.sap.com/hana

Developer

Apache Software Foundation

Esgyn

Google

quasardb

SAP

Initial release

2014

2015

2009

2010

Current release

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

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++, Java

C++

Server operating systems

Linux
Unix
Windows

Linux

hosted

BSD
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

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

HTTP API

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

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

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

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

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

with Hadoop integration

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

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

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)

Cryptographically strong user authentication and audit trail

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.