DBMS > Amazon Redshift vs. KairosDB vs. KeyDB vs. Memcached

System Properties Comparison Amazon Redshift vs. KairosDB vs. KeyDB vs. Memcached

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 Time Series DBMS based on Cassandra or H2

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

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

Website

aws.amazon.com/redshift

github.com/kairosdb/kairosdb

github.com/Snapchat/KeyDB
keydb.dev

www.memcached.org

Technical documentation

docs.aws.amazon.com/redshift

kairosdb.github.io

docs.keydb.dev

github.com/memcached/memcached/wiki

Developer

Amazon (based on PostgreSQL)

EQ Alpha Technology Ltd.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Initial release

2012

2013

2019

2003

Current release

1.2.2, November 2018

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-3

Open Source

BSD license

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

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

FreeBSD
Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

Proprietary protocol

RESP - REdis Serialization Protoco

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control

simple password-based access control and ACL

yes

using SASL (Simple Authentication and Security Layer) protocol

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.