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

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Time Series DBMS for IoT Applications

Primary database model

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

www.bigchaindb.com

www.geomesa.org

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

bigchaindb.readthedocs.io/en/latest

www.geomesa.org/documentation/stable/user/index.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

CCRi and others

Yanza

Initial release

2012

2014

2016

2014

2015

Current release

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

5.0.1, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL v3

Open Source

Apache License 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

Python

Scala

Server operating systems

hosted

Linux
Unix
Windows

Linux

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

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.

Secondary indexes

restricted

yes

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

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

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

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

depending on storage layer

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

depending on storage layer

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

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

depending on storage layer

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

depending on the DBMS used for storage

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.