DBMS > Alibaba Cloud Table Store vs. Apache Drill vs. Microsoft Azure Cosmos DB vs. YottaDB

System Properties Comparison Alibaba Cloud Table Store vs. Apache Drill vs. Microsoft Azure Cosmos DB vs. YottaDB

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Globally distributed, horizontally scalable, multi-model database service

A fast and solid embedded Key-value store

Primary database model

Wide column store

Document store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.25
Rank	#294	Overall
	#12	Wide column stores

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

www.alibabacloud.com/product/table-store

drill.apache.org

azure.microsoft.com/services/cosmos-db

yottadb.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

drill.apache.org/docs

learn.microsoft.com/azure/cosmos-db

yottadb.com/resources/documentation

Developer

Alibaba

Apache Software Foundation

Microsoft

YottaDB, LLC

Initial release

2016

2012

2014

2001

Current release

1.20.3, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

AGPL 3.0

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

Server operating systems

hosted

Linux
OS X
Windows

hosted

Docker
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

by using the Octo plugin

APIs and other access methods

HTTP API

JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Java
Python

C++

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Access rights based on subaccounts and tokens

Depending on the underlying data source

Access rights can be defined down to the item level

Users and groups based on OS-security mechanisms

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.