DBMS > Amazon Aurora vs. Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. KeyDB

System Properties Comparison Amazon Aurora vs. Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. KeyDB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

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

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Document store

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

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

Website

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

cloud.google.com/spanner

github.com/graphite-project/graphite-web

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

graphite.readthedocs.io

docs.keydb.dev

Developer

Amazon

Amazon (based on PostgreSQL)

Google

Chris Davis

EQ Alpha Technology Ltd.

Initial release

2015

2012

2017

2006

2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-3

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

Data scheme

yes

schema-free

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

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

yes

restricted

yes

by using the Redis Search module

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

HTTP API
Sockets

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication with 3 replicas for regional instances.

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

Optimistic locking, atomic execution of commands blocks and scripts

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.