DBMS > IBM Cloudant vs. Memcached vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Redis

System Properties Comparison IBM Cloudant vs. Memcached vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Redis

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

In-memory key-value store, originally intended for caching

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Globally distributed, horizontally scalable, multi-model database service

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

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column 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

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	2.68
Rank	#106	Overall
	#20	Document stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

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

Website

www.ibm.com/products/cloudant

www.memcached.org

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/cosmos-db

redis.com
redis.io

Technical documentation

cloud.ibm.com/docs/Cloudant

github.com/memcached/memcached/wiki

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

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

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2010

2003

1992

2014

2009

Current release

1.6.25, March 2024

1902 (16.0.11328.20222), March 2019

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Bundled with Microsoft Office

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

hosted

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

JSON types

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

All properties auto-indexed by default

yes

with RediSearch module

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

with RediSQL module

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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 (Map-Reduce) in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

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

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

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

Repcached, a Memcached patch, provides this functionallity

none

yes

Implicit feature of the cloud service

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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

yes

Transaction concepts

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

atomic operations within a document possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

but no files for transaction logging

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

User concepts

Access control

Access rights for users can be defined per database

yes

using SASL (Simple Authentication and Security Layer) protocol

a simple user-level security was built in till version Access 2003

Access rights can be defined down to the item level

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.