DBMS > Alibaba Cloud Table Store vs. EsgynDB vs. JaguarDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Alibaba Cloud Table Store vs. EsgynDB vs. JaguarDB vs. Microsoft Azure Cosmos DB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Performant, highly scalable DBMS for AI and IoT applications

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Wide column store

Relational DBMS

Key-value store
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

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.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Website

www.alibabacloud.com/product/table-store

www.esgyn.cn

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

Technical documentation

www.alibabacloud.com/help/en/tablestore

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

Developer

Alibaba

Esgyn

DataJaguar, Inc.

Microsoft

Initial release

2016

2015

2014

Current release

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

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++, Java

C++

the server part. Clients available in other languages

Server operating systems

hosted

Linux

hosted

Data scheme

schema-free

yes

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC

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

Supported programming languages

Java
Python

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

Java Stored Procedures

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

Multi-source replication between multi datacenters

Multi-source replication

yes

Implicit feature of the cloud service

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

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

Access rights based on subaccounts and tokens

fine grained access rights according to SQL-standard

rights management via user accounts

Access rights can be defined down to the item level

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.