DBMS > Apache IoTDB vs. CockroachDB vs. Couchbase vs. FatDB vs. OpenTSDB

System Properties Comparison Apache IoTDB vs. CockroachDB vs. Couchbase vs. FatDB vs. OpenTSDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Scalable Time Series DBMS based on HBase

Primary database model

Time Series DBMS

Relational DBMS

Document store

Document store
Key-value store

Time Series DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Website

iotdb.apache.org

www.cockroachlabs.com

www.couchbase.com

opentsdb.net

Technical documentation

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

www.cockroachlabs.com/docs

docs.couchbase.com

opentsdb.net/docs/build/html/index.html

Developer

Apache Software Foundation

Cockroach Labs

Couchbase, Inc.

FatCloud

currently maintained by Yahoo and other contributors

Initial release

2018

2015

2011

2012

2011

Current release

1.1.0, April 2023

23.1.1, May 2023

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0, commercial license available

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

LGPL

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C, C++, Go and Erlang

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
macOS
Windows

Linux
OS X
Windows

Windows

Linux
Windows

Data scheme

yes

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

SQL

Support of SQL

SQL-like query language

yes, wire compatible with PostgreSQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

Via inetgration in SQL Server

APIs and other access methods

JDBC
Native API

JDBC

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Telnet API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

yes

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

via applications

Triggers

yes

via the TAP protocol

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

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

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Automatic Sharding

Sharding

based on HBase

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 using RAFT

Multi-source replication

including cross data center replication
Source-replica replication

selectable replication factor

based on HBase

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Ephemeral buckets

User concepts

Access control

yes

Role-based access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Can implement custom security layer via applications

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.