DBMS > Amazon Redshift vs. Heroic vs. KeyDB vs. searchxml vs. TinkerGraph

System Properties Comparison Amazon Redshift vs. Heroic vs. KeyDB vs. searchxml vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

DBMS for structured and unstructured content wrapped with an application server

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Native XML DBMS
Search engine

Graph DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

aws.amazon.com/redshift

github.com/spotify/heroic

github.com/Snapchat/KeyDB
keydb.dev

www.searchxml.net/category/products

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.aws.amazon.com/redshift

spotify.github.io/heroic

docs.keydb.dev

www.searchxml.net/support/handouts

Developer

Amazon (based on PostgreSQL)

Spotify

EQ Alpha Technology Ltd.

informationpartners gmbh

Initial release

2012

2014

2019

2015

2009

Current release

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-3

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++

Java

Server operating systems

hosted

Linux

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

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

via Elasticsearch

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API
WebDAV
XQuery
XSLT

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

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++

most other programming languages supported via APIs

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

on the application server

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

multiple readers, single writer

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

optional

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 and ACL

Domain, group and role-based access control at the document level and for application services

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.