DBMS > Microsoft Azure Cosmos DB vs. SAP IQ vs. Snowflake vs. ToroDB

System Properties Comparison Microsoft Azure Cosmos DB vs. SAP IQ vs. Snowflake vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Globally distributed, horizontally scalable, multi-model database service

Columnar RDBMS optimized for Big Data analytics

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column-oriented

Relational DBMS

Document store

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	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

github.com/torodb/server

Technical documentation

learn.microsoft.com/azure/cosmos-db

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

Microsoft

SAP, formerly Sybase

Snowflake Computing Inc.

8Kdata

Initial release

2014

1994

2014

2016

Current release

16.1 SPS04, April 2019

License

Commercial or Open Source

commercial

Open Source

AGPL-V3

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

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, integer, double, boolean, date, object_id

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

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

yes

user defined functions

Triggers

JavaScript

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

SAP/Sybase Replication Server

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Hadoop integration

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

Eventual 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.

User concepts

Access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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

Access rights for users and roles

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.