DBMS > Alibaba Cloud Table Store vs. Amazon Redshift vs. Google Cloud Datastore vs. Microsoft Azure SQL Database vs. RDF4J

System Properties Comparison Alibaba Cloud Table Store vs. Amazon Redshift vs. Google Cloud Datastore vs. Microsoft Azure SQL Database vs. RDF4J

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

Large scale data warehouse service for use with business intelligence tools

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

Database as a Service offering with high compatibility to Microsoft SQL Server

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/redshift

cloud.google.com/datastore

azure.microsoft.com/en-us/products/azure-sql/database

rdf4j.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

docs.microsoft.com/en-us/azure/azure-sql

rdf4j.org/documentation

Developer

Alibaba

Amazon (based on PostgreSQL)

Google

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

2012

2008

2010

2004

Current release

V12

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Server operating systems

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

schema-free

yes

RDF Schemas

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP API

JDBC
ODBC

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

ADO.NET
JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java
Python

All languages supporting JDBC/ODBC

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

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

Transact SQL

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication using Paxos

yes, with always 3 replicas available

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

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic single-row operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

In-memory capabilities

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

yes

User concepts

Access control

Access rights based on subaccounts and tokens

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

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.