DBMS > Amazon Redshift vs. EXASOL vs. Google Cloud Spanner vs. Microsoft Azure Table Storage vs. TigerGraph

System Properties Comparison Amazon Redshift vs. EXASOL vs. Google Cloud Spanner vs. Microsoft Azure Table Storage vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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.

A Wide Column Store for rapid development using massive semi-structured datasets

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Wide column store

Graph DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

www.exasol.com

cloud.google.com/spanner

azure.microsoft.com/en-us/services/storage/tables

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

cloud.google.com/spanner/docs

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Exasol

Google

Microsoft

Initial release

2012

2000

2017

2012

2017

License

Commercial or Open Source

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

C++

Server operating systems

hosted

Linux

Data scheme

yes

schema-free

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

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

Go
Java
JavaScript (Node.js)
Python

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication with 3 replicas for regional instances.

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

yes

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

yes

Relationships in graphs

Transaction concepts

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

ACID

Strict serializable isolation

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles according to SQL-standard

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

Access rights based on private key authentication or shared access signatures

Role-based access control

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.