DBMS > AlaSQL vs. Alibaba Cloud Table Store vs. Amazon DynamoDB vs. FatDB vs. Riak KV

System Properties Comparison AlaSQL vs. Alibaba Cloud Table Store vs. Amazon DynamoDB vs. FatDB vs. Riak KV

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

JavaScript DBMS library

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

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

Distributed, fault tolerant key-value store

Primary database model

Document store
Relational DBMS

Wide column store

Document store
Key-value store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

alasql.org

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

Technical documentation

github.com/AlaSQL/alasql

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

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

Developer

Andrey Gershun & Mathias R. Wulff

Alibaba

Amazon

FatCloud

OpenSource, formerly Basho Technologies

Initial release

2014

2016

2012

2009

Current release

3.2.0, December 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache version 2, commercial enterprise edition

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

JavaScript

Erlang

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Windows

Linux
OS X

Data scheme

schema-free

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

yes

restricted

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

Via inetgration in SQL Server

APIs and other access methods

JavaScript API

HTTP API

RESTful HTTP API

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

HTTP API
Native Erlang Interface

Supported programming languages

JavaScript

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
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

Server-side scripts

Stored procedures

yes

via applications

Erlang

Triggers

yes

by integration with AWS Lambda

yes

via applications

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

yes

only for local storage and DOM-storage

Atomic single-row operations

ACID

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

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

Can implement custom security layer via applications

yes, using Riak Security

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.