DBMS > Apache IoTDB vs. IBM Cloudant vs. PostGIS vs. Tarantool

System Properties Comparison Apache IoTDB vs. IBM Cloudant vs. PostGIS vs. Tarantool

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

Spatial extension of PostgreSQL

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Time Series DBMS

Document store

Spatial DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

with Tarantool/GIS extension

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

iotdb.apache.org

www.ibm.com/products/cloudant

postgis.net

www.tarantool.io

Technical documentation

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

cloud.ibm.com/docs/Cloudant

postgis.net/documentation

www.tarantool.io/en/doc

Developer

Apache Software Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2018

2010

2005

2008

Current release

1.1.0, April 2023

3.4.2, February 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

BSD
Linux
macOS

Data scheme

yes

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL

Support of SQL

SQL-like query language

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
Native API

RESTful HTTP/JSON API

Open binary protocol

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

based on PostgreSQL

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

based on PostgreSQL

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

Access rights for users can be defined per database

yes

based on PostgreSQL

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

IoTDB Provides Data Management for Industrial Edge IT
15 October 2020, The New Stack

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

In-Memory Showdown: Redis vs. Tarantool
4 April 2023, Хабр

TaranHouse: New Big Data Warehouse Announced by Tarantool
4 April 2018, Newswire

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

Deploying Tarantool Cartridge applications with zero effort (Part 2)
13 April 2020, Хабр

Тarantool Cartridge: Sharding Lua Backend in Three Lines
9 October 2019, Хабр

provided by Google News

Share this page