DBMS > Amazon Redshift vs. GridGain vs. InterSystems Caché vs. KairosDB

System Properties Comparison Amazon Redshift vs. GridGain vs. InterSystems Caché vs. KairosDB

Please select another system to include it in the comparison.

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

GridGain is an in-memory computing platform, built on Apache Ignite

A multi-model DBMS and application server

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Secondary database models

Document store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Website

aws.amazon.com/redshift

www.gridgain.com

www.intersystems.com/products/cache

github.com/kairosdb/kairosdb

Technical documentation

docs.aws.amazon.com/redshift

www.gridgain.com/docs/index.html

docs.intersystems.com

kairosdb.github.io

Developer

Amazon (based on PostgreSQL)

GridGain Systems, Inc.

InterSystems

Initial release

2012

2007

1997

2013

Current release

GridGain 8.5.1

2018.1.4, May 2020

1.2.2, November 2018

License

Commercial or Open Source

commercial

commercial, open source

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

Java, C++, .Net, Python, REST, SQL

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows
z/OS

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

Linux
OS X
Windows

Data scheme

yes

depending on used data model

schema-free

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.

yes

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

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

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Java

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

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

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Source-replica replication

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control
Security Hooks for custom implementations

Access rights for users, groups and roles

simple password-based access control

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.