DBMS > Couchbase vs. Google Cloud Firestore vs. IBM Db2 Event Store vs. Redis vs. Splice Machine

System Properties Comparison Couchbase vs. Google Cloud Firestore vs. IBM Db2 Event Store vs. Redis vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Distributed Event Store optimized for Internet of Things use cases

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.

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store

Event Store
Time Series DBMS

Key-value store

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

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series 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	17.30
Rank	#36	Overall
	#5	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

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

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

www.couchbase.com

firebase.google.com/products/firestore

www.ibm.com/products/db2-event-store

redis.com
redis.io

splicemachine.com

Technical documentation

docs.couchbase.com

firebase.google.com/docs/firestore

www.ibm.com/docs/en/db2-event-store

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

splicemachine.com/how-it-works

Developer

Couchbase, Inc.

Google

IBM

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Splice Machine

Initial release

2011

2017

2009

2014

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

2.0

7.2.4, January 2024

3.1, March 2021

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

free developer edition available

Open Source

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

Open Source

AGPL 3.0, commercial license available

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

C, C++, Go and Erlang

C and C++

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux, macOS, Windows for the developer addition

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

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

yes

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

with RediSearch module

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

through the embedded Spark runtime

with RediSQL module

yes

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

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#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes, Firebase Rules & Cloud Functions

yes

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

yes

Java

Triggers

yes

via the TAP protocol

yes, with Cloud Functions

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

Active-active shard replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

through RedisGears

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

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

yes

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Data access is serialized by the server

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

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 rights for users, groups and roles 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.