DBMS > Alibaba Cloud Table Store vs. etcd vs. MySQL vs. Sadas Engine

System Properties Comparison Alibaba Cloud Table Store vs. etcd vs. MySQL vs. Sadas Engine

Please select another system to include it in the comparison.

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

A distributed reliable key-value store

Widely used open source RDBMS

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Wide column store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.25
Rank	#294	Overall
	#12	Wide column stores

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

www.alibabacloud.com/product/table-store

etcd.io
github.com/etcd-io/etcd

www.mysql.com

www.sadasengine.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

dev.mysql.com/doc

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Alibaba

Oracle

since 2010, originally MySQL AB, then Sun

SADAS s.r.l.

Initial release

2016

1995

2006

Current release

3.4, August 2019

9.0.0, July 2024

8.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free trial version 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 and C++

C++

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

HTTP API

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
Proprietary protocol

Supported programming languages

Java
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic single-row operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

managed by 'Learn by Usage'

User concepts

Access control

Access rights based on subaccounts and tokens

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

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.