DBMS > Amazon Redshift vs. Drizzle vs. Riak TS vs. WakandaDB

System Properties Comparison Amazon Redshift vs. Drizzle vs. Riak TS vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Time Series DBMS

Object oriented DBMS

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	#319	Overall
	#27	Time Series DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

aws.amazon.com/redshift

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

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

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Open Source, formerly Basho Technologies

Wakanda SAS

Initial release

2012

2008

2015

2012

Current release

7.2.4, September 2012

3.0.0, September 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

AGPLv3, extended commercial license 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

C++

Erlang

C++, JavaScript

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
OS X

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes, limited

APIs and other access methods

JDBC
ODBC

JDBC

HTTP API
Native Erlang Interface

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

yes

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between datasets can be stored

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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.