DBMS > Amazon Redshift vs. Hive vs. Ignite vs. TerarkDB vs. Yanza

System Properties Comparison Amazon Redshift vs. Hive vs. Ignite vs. TerarkDB 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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

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	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

hive.apache.org

ignite.apache.org

github.com/bytedance/terarkdb

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

cwiki.apache.org/confluence/display/Hive/Home

apacheignite.readme.io/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

initially developed by Facebook

Apache Software Foundation

ByteDance, originally Terark

Yanza

Initial release

2012

2015

2016

2015

Current release

3.1.3, April 2022

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

restricted open source version available

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++, Java, .Net

C++

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Solaris
Windows

Windows

Data scheme

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

SQL-like DML and DDL statements

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
PHP
Python

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

yes (compute grid and cache interceptors can be used instead)

Triggers

yes (cache interceptors and events)

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

selectable replication factor

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

Security Hooks for custom implementations

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.