DBMS > Microsoft Azure Cosmos DB vs. Netezza vs. Snowflake vs. Splunk

System Properties Comparison Microsoft Azure Cosmos DB vs. Netezza vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Data warehouse and analytics appliance part of IBM PureSystems

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

Analytics Platform for Big Data

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

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

Score	7.56
Rank	#48	Overall
	#31	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

azure.microsoft.com/services/cosmos-db

www.ibm.com/products/netezza

www.snowflake.com

www.splunk.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Microsoft

IBM

Snowflake Computing Inc.

Splunk Inc.

Initial release

2014

2000

2014

2003

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

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.

Server operating systems

hosted

Linux

included in appliance

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

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

Splunk Search Processing Language for search commands

APIs and other access methods

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

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

yes

user defined functions

yes

Triggers

JavaScript

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

Users with fine-grained authorization concept

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.