DBMS > Memcached vs. Microsoft Azure SQL Database vs. PostGIS vs. Redis vs. Tkrzw

System Properties Comparison Memcached vs. Microsoft Azure SQL Database vs. PostGIS vs. Redis vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Spatial extension of PostgreSQL

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.

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational 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	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

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

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.memcached.org

azure.microsoft.com/en-us/products/azure-sql/database

postgis.net

redis.com
redis.io

dbmx.net/tkrzw

Technical documentation

github.com/memcached/memcached/wiki

docs.microsoft.com/en-us/azure/azure-sql

postgis.net/documentation

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

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Mikio Hirabayashi

Initial release

2003

2010

2005

2009

2020

Current release

1.6.27, May 2024

V12

3.4.2, February 2024

7.2.5, May 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

GPL v2.0

Open Source

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

Open Source

Apache Version 2.0

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

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
macOS

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.

yes

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

with RediSQL module

APIs and other access methods

Proprietary protocol

ADO.NET
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL

user defined functions

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

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes, with always 3 replicas available

yes

based on PostgreSQL

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

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

using specific database classes

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.