DBMS > Apache IoTDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. PostGIS

System Properties Comparison Apache IoTDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Primary database model

Time Series DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

iotdb.apache.org

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

postgis.net

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

Developer

Apache Software Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2018

2010

2014

2005

Current release

1.1.0, April 2023

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.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

Java

Erlang

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Data scheme

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.

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

JDBC
Native API

RESTful HTTP/JSON API

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

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

JavaScript

user defined functions

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual 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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

yes

Access rights for users can be defined per database

Access rights can be defined down to the item level

yes

based on PostgreSQL

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.