DBMS > CouchDB vs. Faircom EDGE vs. Redis vs. TimescaleDB vs. Yanza

System Properties Comparison CouchDB vs. Faircom EDGE vs. Redis vs. TimescaleDB vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

Document store

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

Spatial DBMS

using the Geocouch extension

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Relational DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

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

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

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

couchdb.apache.org

www.faircom.com/products/faircom-edge

redis.com
redis.io

www.timescale.com

yanza.com

Technical documentation

docs.couchdb.org/en/stable

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

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

docs.timescale.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

FairCom Corporation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Timescale

Yanza

Initial release

2005

1979

2009

2017

2015

Current release

3.3.3, December 2023

V3, October 2020

7.2.4, January 2024

2.13.0, November 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Restricted, free version available

Open Source

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

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Erlang

ANSI C, C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Android
Linux

ARM, x86
Raspbian
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

Windows

Data scheme

schema-free

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

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

partial

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

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

via views

yes

with RediSearch module

yes

SQL

Support of SQL

yes

ANSI SQL queries

with RediSQL module

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

View functions in JavaScript

yes

.Net, JavaScript, C/C++

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

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

File partitioning

Customizable business rules for partitioning

Sharding

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

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication with hot standby and reads on replicas

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

across SQL and NoSQL

yes

Data access is serialized by the server

yes

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

User concepts

Access control

Access rights for users can be defined per database

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

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.