DBMS > Amazon Redshift vs. InterSystems Caché vs. Kinetica vs. Prometheus vs. Riak KV

System Properties Comparison Amazon Redshift vs. InterSystems Caché vs. Kinetica vs. Prometheus vs. Riak KV

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A multi-model DBMS and application server

Fully vectorized database across both GPUs and CPUs

Open-source Time Series DBMS and monitoring system

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Time Series DBMS

Key-value store

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

Secondary database models

Document store

Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

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

Website

aws.amazon.com/redshift

www.intersystems.com/products/cache

www.kinetica.com

prometheus.io

Technical documentation

docs.aws.amazon.com/redshift

docs.intersystems.com

docs.kinetica.com

prometheus.io/docs

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

Developer

Amazon (based on PostgreSQL)

InterSystems

Kinetica

OpenSource, formerly Basho Technologies

Initial release

2012

1997

2012

2015

2009

Current release

2018.1.4, May 2020

7.1, August 2021

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

C, C++

Erlang

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux

Linux
Windows

Linux
OS X

Data scheme

yes

depending on used data model

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

yes

Import of XML data possible

Secondary indexes

restricted

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java

C++
Java
JavaScript (Node.js)
Python

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Erlang

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

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"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

by Federation

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 depending on configuration

none

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

Access rights for users and roles on table level

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.