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

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

Editorial information provided by DB-Engines

Name

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

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Globally distributed, horizontally scalable, multi-model database service

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS
Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series 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

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

druid.apache.org

azure.microsoft.com/services/cosmos-db

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

www.tarantool.io

trafodion.apache.org

Technical documentation

druid.apache.org/docs/latest/design

learn.microsoft.com/azure/cosmos-db

www.tarantool.io/en/doc

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation and contributors

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2012

2014

2012

2008

2014

Current release

29.0.1, April 2024

2.10.0, May 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Java

C and C++

C++, Java

Server operating systems

Linux
OS X
Unix

hosted

BSD
Linux
macOS

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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 for querying

SQL-like query language

Full-featured ANSI SQL support

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

RESTful HTTP API

Open binary protocol

ADO.NET
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

Lua, C and SQL stored procedures

Java Stored Procedures

Triggers

JavaScript

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Implicit feature of the cloud service

yes

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

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.