DBMS > Apache IoTDB vs. Microsoft Azure Cosmos DB vs. Realm vs. SpaceTime

System Properties Comparison Apache IoTDB vs. Microsoft Azure Cosmos DB vs. Realm vs. SpaceTime

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

Globally distributed, horizontally scalable, multi-model database service

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document 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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

iotdb.apache.org

azure.microsoft.com/services/cosmos-db

realm.io

www.mireo.com/spacetime

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

realm.io/docs

Developer

Apache Software Foundation

Microsoft

Realm, acquired by MongoDB in May 2019

Mireo

Initial release

2018

2014

2020

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

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

Java

C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Android
Backend: server-less
iOS
Windows

Linux

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
Native API

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

RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
C++
Python

Server-side scripts

Stored procedures

yes

JavaScript

runs within the applications so server-side scripts are unnecessary

Triggers

yes

JavaScript

yes

Change Listeners

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

none

Fixed-grid hypercubes

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

yes

Implicit feature of the cloud service

none

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

In-Memory realm

User concepts

Access control

yes

Access rights can be defined down to the item level

yes

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.