DBMS > Apache IoTDB vs. Couchbase vs. Machbase Neo vs. Trafodion

System Properties Comparison Apache IoTDB vs. Couchbase vs. Machbase Neo vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines 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

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

TimeSeries DBMS for AIoT and BigData

Transactional SQL-on-Hadoop DBMS

Primary database model

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	#164	Overall
	#14	Time Series DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Website

Technical documentation

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

docs.couchbase.com

machbase.com/dbms

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Couchbase, Inc.

Machbase

Apache Software Foundation, originally developed by HP

Initial release

2018

2011

2013

2014

Current release

1.1.0, April 2023

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

V8.0, August 2023

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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

commercial

free test version available

Open Source

Apache 2.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

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

Linux
macOS
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

SQL-like query language

yes

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

selectable replication factor

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

via user defined functions and HBase

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

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

yes

volatile and lookup table

User concepts

Access control

yes

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

simple password-based access control

fine grained access rights according to SQL-standard

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.