DBMS > Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. Tarantool vs. WakandaDB

System Properties Comparison Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. Tarantool vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Object oriented DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

cloud.google.com/spanner

github.com/graphite-project/graphite-web

www.tarantool.io

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

graphite.readthedocs.io

www.tarantool.io/en/doc

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Google

Chris Davis

Wakanda SAS

Initial release

2012

2017

2006

2008

2012

Current release

2.10.0, May 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

AGPLv3, extended commercial license available

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

C++, JavaScript

Server operating systems

hosted

Linux
Unix

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

Numeric data only

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

Full-featured ANSI SQL support

APIs and other access methods

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

Open binary protocol

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

Lua, C and SQL stored procedures

yes

Triggers

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication with 3 replicas for regional instances.

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

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

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

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)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

yes

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.