DBMS > Amazon Redshift vs. Google Cloud Spanner vs. SpaceTime vs. VoltDB

System Properties Comparison Amazon Redshift vs. Google Cloud Spanner vs. SpaceTime vs. VoltDB

Please select another system to include it in the comparison.

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.

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

cloud.google.com/spanner

www.mireo.com/spacetime

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Google

Mireo

VoltDB Inc.

Initial release

2012

2017

2020

2010

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

hosted

Linux

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

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

A subset of ANSI SQL is implemented

yes

only a subset of SQL 99

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

RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

C#
C++
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Fixed-grid hypercubes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication with 3 replicas for regional instances.

Real-time block device replication (DRBD)

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

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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)

yes

Users and roles with access to stored procedures

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.