DBMS > CouchDB vs. Datomic vs. Google Cloud Bigtable vs. PouchDB vs. Redis

System Properties Comparison CouchDB vs. Datomic vs. Google Cloud Bigtable vs. PouchDB vs. Redis

Editorial information provided by DB-Engines

Name

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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.

Primary database model

Document store

Relational DBMS

Key-value store
Wide column store

Document store

Key-value store

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

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

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Website

couchdb.apache.org

www.datomic.com

cloud.google.com/bigtable

pouchdb.com

redis.com
redis.io

Technical documentation

docs.couchdb.org/en/stable

docs.datomic.com

cloud.google.com/bigtable/docs

pouchdb.com/guides

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

Developer

Apache Software Foundation

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

Cognitect

Google

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2005

2012

2015

2012

2009

Current release

3.3.3, December 2023

1.0.6735, June 2023

7.1.1, June 2019

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

limited edition free

commercial

Open Source

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

Cloud-based only

Only available as a cloud service

yes

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

Java, Clojure

JavaScript

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

hosted

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

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

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

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

via views

yes

with RediSearch module

SQL

Support of SQL

with RediSQL module

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

Clojure
Java

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

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

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Transaction Functions

View functions in JavaScript

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

Triggers

yes

By using transaction functions

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

But extensive use of caching in the application peers

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

But extensive use of caching in the application peers

Internal replication in Colossus, and regional replication between two clusters in different zones

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

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

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

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

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

ACID

Atomic single-row operations

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.