DBMS > Apache IoTDB vs. Elasticsearch vs. Faircom EDGE vs. Redis vs. RRDtool

System Properties Comparison Apache IoTDB vs. Elasticsearch vs. Faircom EDGE vs. Redis vs. RRDtool

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, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Time Series DBMS

Search engine

Key-value store
Relational DBMS

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
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	135.35
Rank	#7	Overall
	#1	Search engines

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

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

iotdb.apache.org

www.elastic.co/elasticsearch

www.faircom.com/products/faircom-edge

redis.com
redis.io

oss.oetiker.ch/rrdtool

Technical documentation

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

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

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

docs.redis.com/latest/index.html
redis.io/docs

oss.oetiker.ch/rrdtool/doc

Developer

Apache Software Foundation

Elastic

FairCom Corporation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Tobias Oetiker

Initial release

2018

2010

1979

2009

1999

Current release

1.1.0, April 2023

8.6, January 2023

V3, October 2020

7.2.4, January 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic License

commercial

Restricted, free version available

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

GPL V2 and FLOSS

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

ANSI C, C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java VM

Android
Linux

ARM, x86
Raspbian
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

HP-UX
Linux

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

All search fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language

yes

ANSI SQL queries

with RediSQL module

APIs and other access methods

JDBC
Native API

Java API
RESTful HTTP/JSON API

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

proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library
Pipes

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

by using the 'percolation' feature

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

none

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

ES-Hadoop Connector

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency
Tunable Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

none

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Data access is serialized by the server

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

yes

Memcached and Redis integration

yes

User concepts

Access control

yes

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

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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.