DBMS > Heroic vs. Microsoft Azure Cosmos DB vs. Netezza vs. NuoDB

System Properties Comparison Heroic vs. Microsoft Azure Cosmos DB vs. Netezza vs. NuoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Globally distributed, horizontally scalable, multi-model database service

Data warehouse and analytics appliance part of IBM PureSystems

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Website

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

www.ibm.com/products/netezza

www.3ds.com/nuodb-distributed-sql-database

Technical documentation

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

doc.nuodb.com

Developer

Spotify

Microsoft

IBM

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2014

2000

2013

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

limited edition free

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

Server operating systems

hosted

Linux

included in appliance

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

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

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC

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

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

Server-side scripts

Stored procedures

JavaScript

yes

Java, SQL

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

data is dynamically stored/cached on the nodes where it is read/written

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

yes

Managed transparently by NuoDB

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

Eventual Consistency
Immediate Consistency

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

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Temporary table

User concepts

Access control

Access rights can be defined down to the item level

Users with fine-grained authorization concept

Standard SQL roles/ privileges, Administrative Users

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.