DBMS > Microsoft Azure Cosmos DB vs. Snowflake vs. Tkrzw vs. Trafodion

System Properties Comparison Microsoft Azure Cosmos DB vs. Snowflake vs. Tkrzw 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

Globally distributed, horizontally scalable, multi-model database service

Cloud-based data warehousing service for structured and semi-structured data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

azure.microsoft.com/services/cosmos-db

www.snowflake.com

dbmx.net/tkrzw

trafodion.apache.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Microsoft

Snowflake Computing Inc.

Mikio Hirabayashi

Apache Software Foundation, originally developed by HP

Initial release

2014

2020

2014

Current release

0.9.3, August 2020

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

C++, Java

Server operating systems

hosted

Linux
macOS

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

user defined functions

Java Stored Procedures

Triggers

JavaScript

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

none

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

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

ACID

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.

yes

using specific database classes

User concepts

Access control

Access rights can be defined down to the item level

Users with fine-grained authorization concept, user roles and pluggable authentication

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.