DBMS > Amazon Redshift vs. Ignite vs. InterSystems Caché vs. Kinetica vs. Prometheus

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

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A multi-model DBMS and application server

Fully vectorized database across both GPUs and CPUs

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Time Series DBMS

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

aws.amazon.com/redshift

ignite.apache.org

www.intersystems.com/products/cache

www.kinetica.com

prometheus.io

Technical documentation

docs.aws.amazon.com/redshift

apacheignite.readme.io/docs

docs.intersystems.com

docs.kinetica.com

prometheus.io/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

InterSystems

Kinetica

Initial release

2012

2015

1997

2012

2015

Current release

Apache Ignite 2.6

2018.1.4, May 2020

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

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++, Java, .Net

C, C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

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

Linux

Linux
Windows

Data scheme

yes

depending on used data model

yes

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Java

C++
Java
JavaScript (Node.js)
Python

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes (compute grid and cache interceptors can be used instead)

yes

user defined functions

Triggers

yes (cache interceptors and events)

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Source-replica replication

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

Security Hooks for custom implementations

Access rights for users, groups and roles

Access rights for users and roles on table level

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.