DBMS > Alibaba Cloud Table Store vs. Google Cloud Firestore vs. Microsoft Azure Table Storage vs. Riak TS vs. RocksDB

System Properties Comparison Alibaba Cloud Table Store vs. Google Cloud Firestore vs. Microsoft Azure Table Storage vs. Riak TS vs. RocksDB

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A Wide Column Store for rapid development using massive semi-structured datasets

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.alibabacloud.com/product/table-store

firebase.google.com/products/firestore

azure.microsoft.com/en-us/services/storage/tables

rocksdb.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

firebase.google.com/docs/firestore

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

github.com/facebook/rocksdb/wiki

Developer

Alibaba

Google

Microsoft

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2016

2017

2012

2015

2013

Current release

3.0.0, September 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

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

Linux

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

yes, limited

APIs and other access methods

HTTP API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Java
Python

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C#
C++
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++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Erlang

Triggers

yes, with Cloud Functions

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

Atomic single-row operations

yes

optimistic locking

yes

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights based on private key authentication or shared access signatures

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.