DBMS > Amazon Redshift vs. Faircom DB vs. HBase vs. Riak KV

System Properties Comparison Amazon Redshift vs. Faircom DB vs. HBase vs. Riak KV

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Wide-column store based on Apache Hadoop and on concepts of BigTable

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Wide column store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-db

hbase.apache.org

Technical documentation

docs.aws.amazon.com/redshift

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

hbase.apache.org/book.html

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

Apache Software Foundation

Apache top-level project, originally developed by Powerset

OpenSource, formerly Basho Technologies

Initial release

2012

1979

2008

2009

Current release

V12, November 2020

2.3.4, January 2021

3.2.0, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache version 2

Open Source

Apache version 2, commercial enterprise edition

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

ANSI C, C++

Java

Erlang

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
Unix
Windows

using Cygwin

Linux
OS X

Data scheme

yes

schema free, schema optional, schema required, partial schema,

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

options to bring your own types, AVRO

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

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, ANSI SQL with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java API
RESTful HTTP API
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C#
C++
Groovy
Java
PHP
Python
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

yes

Coprocessors in Java

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency or Eventual Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

yes, using Riak Security

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.