DBMS > Amazon Redshift vs. Google Cloud Datastore vs. Riak TS vs. SAP IQ vs. TigerGraph

System Properties Comparison Amazon Redshift vs. Google Cloud Datastore vs. Riak TS vs. SAP IQ vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Columnar RDBMS optimized for Big Data analytics

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

Primary database model

column-oriented

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

cloud.google.com/datastore

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

www.tiot.jp/riak-docs/riak/ts/latest

help.sap.com/docs/SAP_IQ

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Google

Open Source, formerly Basho Technologies

SAP, formerly Sybase

Initial release

2012

2008

2015

1994

2017

Current release

3.0.0, September 2022

16.1 SPS04, April 2019

License

Commercial or Open Source

commercial

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

Erlang

C++

Server operating systems

hosted

Linux
OS X

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

yes, limited

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC
RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Java
Perl
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

Erlang

yes

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

selectable replication factor

SAP/Sybase Replication Server

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

links between datasets can be stored

yes

Relationships in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.