DBMS > Amazon Redshift vs. Apache Phoenix vs. BigchainDB vs. CouchDB vs. Yanza

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	8.30
Rank	#47	Overall
	#7	Document stores

Website

aws.amazon.com/redshift

phoenix.apache.org

www.bigchaindb.com

couchdb.apache.org

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

bigchaindb.readthedocs.io/en/latest

docs.couchdb.org/en/stable

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Yanza

Initial release

2012

2014

2016

2005

2015

Current release

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

3.3.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL v3

Open Source

Apache version 2

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

Python

Erlang

Server operating systems

hosted

Linux
Unix
Windows

Linux

Android
BSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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.

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

JDBC

CLI Client
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

View functions in JavaScript

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

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

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

atomic operations within a single document possible

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

Access rights for users can be defined per database

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.