DBMS > Alibaba Cloud Table Store vs. Faircom DB vs. Microsoft SQL Server vs. Riak KV vs. Vitess

System Properties Comparison Alibaba Cloud Table Store vs. Faircom DB vs. Microsoft SQL Server vs. Riak KV vs. Vitess

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Microsofts flagship relational DBMS

Distributed, fault tolerant key-value store

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Wide column store

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.alibabacloud.com/product/table-store

www.faircom.com/products/faircom-db

www.microsoft.com/en-us/sql-server

vitess.io

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

learn.microsoft.com/en-US/sql/sql-server

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

vitess.io/docs

Developer

Alibaba

FairCom Corporation

Microsoft

OpenSource, formerly Basho Technologies

The Linux Foundation, PlanetScale

Initial release

2016

1979

1989

2009

2013

Current release

V12, November 2020

SQL Server 2022, November 2022

3.2.0, December 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache Version 2.0, commercial licenses available

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

ANSI C, C++

C++

Erlang

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
Windows

Linux
OS X

Docker
Linux
macOS

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

restricted

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP API
Native Erlang Interface

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
Python

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Erlang

yes

proprietary syntax

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes, but depending on the SQL-Server Edition

selectable replication factor

Multi-source replication
Source-replica replication

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
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

tunable from ACID to Eventually Consistent

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

fine grained access rights according to SQL-standard

yes, using Riak Security

Users with fine-grained authorization concept

no user groups or roles

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.