DBMS > Amazon Redshift vs. Apache Kylin vs. Ignite vs. KeyDB vs. Tkrzw

System Properties Comparison Amazon Redshift vs. Apache Kylin vs. Ignite vs. KeyDB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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.

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store
Relational 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	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/redshift

kylin.apache.org

ignite.apache.org

github.com/Snapchat/KeyDB
keydb.dev

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

kylin.apache.org/docs

apacheignite.readme.io/docs

docs.keydb.dev

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation, originally contributed from eBay Inc

Apache Software Foundation

EQ Alpha Technology Ltd.

Mikio Hirabayashi

Initial release

2012

2015

2019

2020

Current release

3.1.0, July 2020

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

BSD-3

Open Source

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

C++

Server operating systems

hosted

Linux

Linux
OS X
Solaris
Windows

Linux

Linux
macOS

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.

yes

Secondary indexes

restricted

yes

by using the Redis Search module

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for queries (using Apache Calcite)

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

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

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

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

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

Lua

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

simple password-based access control and ACL

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.