DBMS > Amazon Redshift vs. HBase vs. Machbase Neo vs. Riak KV

System Properties Comparison Amazon Redshift vs. HBase vs. Machbase Neo 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

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

TimeSeries DBMS for AIoT and BigData

Distributed, fault tolerant key-value store

Primary database model

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	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Website

aws.amazon.com/redshift

hbase.apache.org

machbase.com

Technical documentation

docs.aws.amazon.com/redshift

hbase.apache.org/book.html

machbase.com/dbms

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

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Machbase

OpenSource, formerly Basho Technologies

Initial release

2012

2008

2013

2009

Current release

2.3.4, January 2021

V8.0, August 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

free test version available

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

Java

Erlang

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Linux
macOS
Windows

Linux
OS X

Data scheme

yes

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
Thrift

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

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
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

Coprocessors in Java

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Immediate Consistency or Eventual Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between data sets can be stored

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

simple password-based access control

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.