DBMS > Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Blazegraph vs. PlanetScale vs. Titan

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Blazegraph vs. PlanetScale vs. Titan

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Wide column store

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Graph DBMS

Secondary database models

Document store
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	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

blazegraph.com

planetscale.com

github.com/thinkaurelius/titan

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

wiki.blazegraph.com

planetscale.com/docs

github.com/thinkaurelius/titan/wiki

Developer

Alibaba

Amazon

Blazegraph

PlanetScale

Aurelius, owned by DataStax

Initial release

2016

2012

2006

2020

2012

Current release

2.1.5, March 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

extended commercial license available

commercial

Open Source

Apache license, version 2.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

Java

Server operating systems

hosted

Linux
OS X
Windows

Docker
Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

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

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

APIs and other access methods

HTTP API

RESTful HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
MySQL protocol
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

not for MyISAM storage engine

yes

Relationships in graph

Transaction concepts

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

Atomic single-row operations

ACID

ACID across one or more tables within a single AWS account and region

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Security and Authentication via Web Application Container (Tomcat, Jetty)

Users with fine-grained authorization concept

no user groups or roles

User authentification and security via Rexster Graph Server

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.