DBMS > Amazon Redshift vs. Graphite vs. KeyDB vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere

System Properties Comparison Amazon Redshift vs. Graphite vs. KeyDB vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

Database as a Service offering with high compatibility to Microsoft SQL Server

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

aws.amazon.com/redshift

github.com/graphite-project/graphite-web

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/redshift

graphite.readthedocs.io

docs.keydb.dev

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon (based on PostgreSQL)

Chris Davis

EQ Alpha Technology Ltd.

Microsoft

SAP

formerly Sybase

Initial release

2012

2006

2019

2010

1992

Current release

V12

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-3

commercial

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

Python

C++

Server operating systems

hosted

Linux
Unix

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

HTTP API
Sockets

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript (Node.js)
Python

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

Transact SQL

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

yes, with always 3 replicas available

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

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

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.