DBMS > Apache Phoenix vs. H2 vs. Snowflake vs. Transbase vs. Yanza

System Properties Comparison Apache Phoenix vs. H2 vs. Snowflake vs. Transbase vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Cloud-based data warehousing service for structured and semi-structured data

A resource-optimized, high-performance, universally applicable RDBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

phoenix.apache.org

www.h2database.com

www.snowflake.com

www.transaction.de/en/products/transbase.html

yanza.com

Technical documentation

phoenix.apache.org

www.h2database.com/html/main.html

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation

Thomas Mueller

Snowflake Computing Inc.

Transaction Software GmbH

Yanza

Initial release

2014

2005

2014

1987

2015

Current release

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

2.2.220, July 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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

commercial

free development license

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C and C++

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

JDBC
ODBC

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

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

Java

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures and User-Defined Functions

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.