DBMS > Amazon Redshift vs. Memcached vs. Riak KV vs. SpaceTime

System Properties Comparison Amazon Redshift vs. Memcached vs. Riak KV vs. SpaceTime

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

In-memory key-value store, originally intended for caching

Distributed, fault tolerant key-value store

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Key-value store

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

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

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

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

aws.amazon.com/redshift

www.memcached.org

www.mireo.com/spacetime

Technical documentation

docs.aws.amazon.com/redshift

github.com/memcached/memcached/wiki

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

Developer

Amazon (based on PostgreSQL)

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

OpenSource, formerly Basho Technologies

Mireo

Initial release

2012

2003

2009

2020

Current release

1.6.27, May 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

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

Erlang

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X

Linux

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC

Proprietary protocol

HTTP API
Native Erlang Interface

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

selectable replication factor

Real-time block device replication (DRBD)

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

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

yes, using Riak Security

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.