DBMS > Amazon Redshift vs. Apache Phoenix vs. Oracle NoSQL vs. Yanza

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Oracle NoSQL 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

Large scale data warehouse service for use with business intelligence tools

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

www.oracle.com/database/nosql/technologies/nosql

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Oracle

Yanza

Initial release

2012

2014

2011

2015

Current release

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

23.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Server operating systems

hosted

Linux
Unix
Windows

Linux
Solaris SPARC/x86

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC

RESTful HTTP API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

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

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

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

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users and roles

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.