DBMS > Amazon DocumentDB vs. Infobright vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Netezza

System Properties Comparison Amazon DocumentDB vs. Infobright vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Netezza

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Globally distributed, horizontally scalable, multi-model database service

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

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational 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	9.06
Rank	#46	Overall
	#29	Relational DBMS

Website

aws.amazon.com/documentdb

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/services/cosmos-db

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

www.ibm.com/products/netezza

Technical documentation

aws.amazon.com/documentdb/resources

learn.microsoft.com/azure/cosmos-db

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

IBM

Initial release

2019

2005

2014

2012

2000

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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

Server operating systems

hosted

Linux
Windows

hosted

Linux

included in appliance

Data scheme

schema-free

yes

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

Knowledge Grid Technology used instead

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

ADO.NET
JDBC
ODBC

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

RESTful HTTP API

JDBC
ODBC
OLE DB

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.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++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Source-replica replication

yes

Implicit feature of the cloud service

yes

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-document operations

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

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.