DBMS > Amazon Redshift vs. Apache Phoenix vs. Graph Engine vs. Machbase Neo vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Graph Engine vs. Machbase Neo vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Key-value store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	2.02
Rank	#130	Overall
	#63	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

aws.amazon.com/redshift

phoenix.apache.org

www.graphengine.io

machbase.com

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

www.graphengine.io/docs/manual

machbase.com/dbms

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Microsoft

Machbase

ByteDance, originally Terark

Initial release

2012

2014

2010

2013

2016

Current release

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

V8.0, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

MIT License

commercial

free test version available

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

.NET and C

C++

Server operating systems

hosted

Linux
Unix
Windows

.NET

Linux
macOS
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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
F#
Visual Basic

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual 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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

volatile and lookup table

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

simple password-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.