DBMS > Apache Phoenix vs. Quasardb vs. Snowflake vs. Yanza

System Properties Comparison Apache Phoenix vs. Quasardb vs. Snowflake vs. Yanza

Please select another system to include it in the comparison.

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

Distributed, high-performance timeseries database

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

Time Series DBMS for IoT Applications

Primary database model

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

phoenix.apache.org

quasar.ai

www.snowflake.com

yanza.com

Technical documentation

phoenix.apache.org

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

quasardb

Snowflake Computing Inc.

Yanza

Initial release

2014

2009

2014

2015

Current release

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

3.14.1, January 2024

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

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

Server operating systems

Linux
Unix
Windows

BSD
Linux
OS X
Windows

hosted

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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

schema-free

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.

yes

Secondary indexes

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC

HTTP API

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

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

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

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

with 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

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

User concepts

Access control

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

Cryptographically strong user authentication and audit trail

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

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.