DBMS > BigObject vs. IBM Db2 vs. Microsoft Azure Cosmos DB vs. NSDb

System Properties Comparison BigObject vs. IBM Db2 vs. Microsoft Azure Cosmos DB vs. NSDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Common in IBM host environments, 2 different versions for host and Windows/Linux

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

bigobject.io

www.ibm.com/products/db2

azure.microsoft.com/services/cosmos-db

nsdb.io

Technical documentation

docs.bigobject.io

www.ibm.com/docs/en/db2

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

Developer

BigObject, Inc.

IBM

Microsoft

Initial release

2015

1983

host version

2014

2017

Current release

12.1, October 2016

License

Commercial or Open Source

commercial

free community edition available

commercial

free version is available

commercial

Open Source

Apache Version 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 and C++

Java, Scala

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

AIX
HP-UX
Linux
Solaris
Windows
z/OS

hosted

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

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

gRPC
HTTP REST
WebSocket

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

Java
Scala

Server-side scripts

Stored procedures

Lua

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

with separate tools (MQ, InfoSphere)

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.