DBMS > Oracle Berkeley DB vs. PouchDB vs. Redis vs. STSdb vs. TimescaleDB

System Properties Comparison Oracle Berkeley DB vs. PouchDB vs. Redis vs. STSdb vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

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

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

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Time Series DBMS

Secondary database models

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	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	2.35
Rank	#116	Overall
	#22	Document stores

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

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Score	4.87
Rank	#74	Overall
	#4	Time Series DBMS

Website

www.oracle.com/database/technologies/related/berkeleydb.html

pouchdb.com

redis.com
redis.io

github.com/STSSoft/STSdb4

www.timescale.com

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

pouchdb.com/guides

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

docs.timescale.com

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

STS Soft SC

Timescale

Initial release

1994

2012

2009

2011

2017

Current release

18.1.40, May 2020

7.1.1, June 2019

7.2.4, January 2024

4.0.8, September 2015

2.13.0, November 2023

License

Commercial or Open Source

Open Source

commercial license available

Open Source

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

Open Source

GPLv2, commercial license 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.

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

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

JavaScript

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

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

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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)

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

via views

yes

with RediSearch module

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

with RediSQL module

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API

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

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

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

only for the SQL API

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

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

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Source-replica replication with hot standby and reads on replicas

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

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

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