DBMS > Alibaba Cloud Table Store vs. Drizzle vs. FatDB vs. Vitess

System Properties Comparison Alibaba Cloud Table Store vs. Drizzle vs. FatDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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 fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Wide column store

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.alibabacloud.com/product/table-store

vitess.io

Technical documentation

www.alibabacloud.com/help/en/tablestore

vitess.io/docs

Developer

Alibaba

Drizzle project, originally started by Brian Aker

FatCloud

The Linux Foundation, PlanetScale

Initial release

2016

2008

2012

2013

Current release

7.2.4, September 2012

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

HTTP API

JDBC

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
Python

C
C++
Java
PHP

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

via applications

yes

proprietary syntax

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Top data analytics tools comparison: Alibaba Cloud, AWS, Azure, Google Cloud, IBM
5 December 2019, Wire19

Apache Software Foundation Announces New Top-Level Project Apache Paimon
16 April 2024, Datanami

Gartner’s Magic Quadrant for Cloud Database Management Systems
9 December 2020, CRN

25 Best Cloud Service Providers (Public and Private) in 2024
4 June 2023, CybersecurityNews

Apache Software Foundation Announces New Top-Level Project Apache Paimon
19 April 2024, Datanami

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page