DBMS > Alibaba Cloud Table Store vs. Amazon Aurora vs. FatDB vs. KairosDB vs. Snowflake

System Properties Comparison Alibaba Cloud Table Store vs. Amazon Aurora vs. FatDB vs. KairosDB vs. Snowflake

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

MySQL and PostgreSQL compatible cloud service by Amazon

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Distributed Time Series DBMS based on Cassandra or H2

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Wide column store

Relational DBMS

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/rds/aurora

github.com/kairosdb/kairosdb

www.snowflake.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

kairosdb.github.io

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Amazon

FatCloud

Snowflake Computing Inc.

Initial release

2016

2015

2012

2013

2014

Current release

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

hosted

Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Graphite protocol
HTTP REST
Telnet API

CLI Client
JDBC
ODBC

Supported programming languages

Java
Python

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

Java
JavaScript

Node.js
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Triggers

yes

via applications

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

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

Access rights based on subaccounts and tokens

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.