DBMS > Amazon Redshift vs. Apache Phoenix vs. Tibero vs. TigerGraph vs. Yanza

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Tibero vs. TigerGraph vs. Yanza

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 secure RDBMS, designed for easy portability from Oracle

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Graph 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	1.78
Rank	#140	Overall
	#64	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

us.tmaxsoft.com/products/tibero

www.tigergraph.com

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

TmaxSoft

Yanza

Initial release

2012

2014

2003

2017

2015

Current release

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

6, April 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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 Assembler

C++

Server operating systems

hosted

Linux
Unix
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Persistent Stored Procedure (PSM)

yes

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by range, hash, list or composite

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

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

In-memory capabilities

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

yes

planned for next version

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

Role-based access control

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.