DBMS > Amazon Redshift vs. Quasardb vs. Riak KV vs. VelocityDB

System Properties Comparison Amazon Redshift vs. Quasardb vs. Riak KV vs. VelocityDB

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

Distributed, high-performance timeseries database

Distributed, fault tolerant key-value store

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

Graph DBMS
Object oriented DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

aws.amazon.com/redshift

quasar.ai

velocitydb.com

Technical documentation

docs.aws.amazon.com/redshift

doc.quasar.ai/master

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

velocitydb.com/UserGuide

Developer

Amazon (based on PostgreSQL)

quasardb

OpenSource, formerly Basho Technologies

VelocityDB Inc

Initial release

2012

2009

2011

Current release

3.14.1, January 2024

3.2.0, December 2022

7.x

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

Server operating systems

hosted

BSD
Linux
OS X
Windows

Linux
OS X

Any that supports .NET

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

HTTP API

HTTP API
Native Erlang Interface

.Net

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication with selectable replication factor

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

links between data sets 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

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

yes, using Riak Security

Based on Windows Authentication

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.