DBMS > Apache IoTDB vs. Couchbase vs. EsgynDB vs. JaguarDB

System Properties Comparison Apache IoTDB vs. Couchbase vs. EsgynDB vs. JaguarDB

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

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Time Series DBMS

Document store

Relational DBMS

Key-value store
Vector 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.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Website

Technical documentation

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

docs.couchbase.com

www.jaguardb.com/support.html

Developer

Apache Software Foundation

Couchbase, Inc.

Esgyn

DataJaguar, Inc.

Initial release

2018

2011

2015

Current release

1.1.0, April 2023

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

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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

commercial

Open Source

GPL V3.0

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

C++, Java

C++

the server part. Clients available in other languages

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
Native API

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

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

Java Stored Procedures

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

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

Automatic Sharding

Sharding

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

including cross data center replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication

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

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

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

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

fine grained access rights according to SQL-standard

rights management via user accounts

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.