DBMS > Amazon Redshift vs. Apache Phoenix vs. Bangdb vs. Linter

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Bangdb vs. Linter

Please select another system to include it in the comparison.

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

Converged and high performance database for device data, events, time series, document and graph

RDBMS for high security requirements

Primary database model

Relational DBMS

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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.07
Rank	#346	Overall
	#47	Document stores
	#35	Graph DBMS
	#32	Time Series DBMS

Score	0.03
Rank	#368	Overall
	#156	Relational DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

bangdb.com

linter.ru

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

docs.bangdb.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Sachin Sinha, BangDB

relex.ru

Initial release

2012

2014

2012

1990

Current release

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

BangDB 2.0, October 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD 3

commercial

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

C, C++

C and C++

Server operating systems

hosted

Linux
Unix
Windows

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL like support with command line tool

yes

APIs and other access methods

JDBC
ODBC

JDBC

Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C#
C++
Java
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor, Knob for CAP (enterprise version only)

Source-replica replication

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

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes

yes, run db with in-memory only mode

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 (enterprise version only)

fine grained access rights according to SQL-standard

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.