DBMS > Apache Drill vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Trafodion

System Properties Comparison Apache Drill vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

drill.apache.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

trafodion.apache.org

Technical documentation

drill.apache.org/docs

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2012

2014

2012

2014

Current release

1.20.3, January 2023

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 2.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

C++, Java

Server operating systems

Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

C++

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

JavaScript

Java Stored Procedures

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

fine grained access rights 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.