DBMS > PouchDB vs. Redis vs. STSdb vs. Tarantool vs. TerarkDB

System Properties Comparison PouchDB vs. Redis vs. STSdb vs. Tarantool vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS with an API inspired by CouchDB

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.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Key-value store

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

Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

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

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

pouchdb.com

redis.com
redis.io

github.com/STSSoft/STSdb4

www.tarantool.io

github.com/bytedance/terarkdb

Technical documentation

pouchdb.com/guides

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

www.tarantool.io/en/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

STS Soft SC

ByteDance, originally Terark

Initial release

2012

2009

2011

2008

2016

Current release

7.1.1, June 2019

7.2.5, May 2024

4.0.8, September 2015

2.10.0, May 2022

License

Commercial or Open Source

Open Source

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

Open Source

GPLv2, commercial license available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

restricted open source version available

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

JavaScript

C and C++

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

partial

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

yes

primitive types and user defined types (classes)

string, double, decimal, uuid, integer, blob, boolean, datetime

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

via views

yes

with RediSearch module

yes

SQL

Support of SQL

with RediSQL module

Full-featured ANSI SQL support

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API

Open binary protocol

C++ API
Java API

Supported programming languages

JavaScript

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

C#
Java

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

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

Lua, C and SQL stored procedures

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

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

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts and optimistic locking

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.