DBMS > Apache IoTDB vs. Couchbase vs. EJDB vs. Faircom EDGE vs. Oracle NoSQL

System Properties Comparison Apache IoTDB vs. Couchbase vs. EJDB vs. Faircom EDGE vs. Oracle NoSQL

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Time Series DBMS

Document store

Key-value store
Relational DBMS

Document store
Key-value store
Relational 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	17.30
Rank	#36	Overall
	#5	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

iotdb.apache.org

www.couchbase.com

github.com/Softmotions/ejdb

www.faircom.com/products/faircom-edge

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

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

docs.couchbase.com

github.com/Softmotions/ejdb/blob/master/README.md

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Apache Software Foundation

Couchbase, Inc.

Softmotions

FairCom Corporation

Oracle

Initial release

2018

2011

2012

1979

2011

Current release

1.1.0, April 2023

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

V3, October 2020

23.3, December 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

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

Open Source

GPLv2

commercial

Restricted, free version available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

ANSI C, C++

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

server-less

Android
Linux

ARM, x86
Raspbian
Windows

Linux
Solaris SPARC/x86

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, ANSI Standard SQL Types

optional

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

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

yes

ANSI SQL queries

SQL-like DML and DDL statements

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

in-process shared library

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

yes

.Net, JavaScript, C/C++

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

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

Automatic Sharding

none

File partitioning

Customizable business rules for partitioning

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

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

with Hadoop integration

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
Tunable Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

when using SQL

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

across SQL and NoSQL

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

off heap cache

User concepts

Access control

yes

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Access rights for 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.