DBMS > Datomic vs. Percona Server for MySQL vs. Redis vs. SingleStore

System Properties Comparison Datomic vs. Percona Server for MySQL vs. Redis vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

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.

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Relational 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

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	2.06
Rank	#118	Overall
	#57	Relational DBMS

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

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

www.datomic.com

www.percona.com/software/mysql-database/percona-server

redis.com
redis.io

www.singlestore.com

Technical documentation

docs.datomic.com

www.percona.com/downloads/Percona-Server-LATEST

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

docs.singlestore.com

Developer

Cognitect

Percona

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SingleStore Inc.

Initial release

2012

2008

2009

2013

Current release

1.0.7180, July 2024

8.0.36-28, 2024

7.2.5, May 2024

8.5, January 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPL version 2

Open Source

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

commercial

free developer edition available

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.

Implementation language

Java, Clojure

C and C++

C++, Go

Server operating systems

All OS with a Java VM

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

64 bit version required

Data scheme

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.

yes

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

yes

with RediSQL module

yes

but no triggers and foreign keys

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

Clojure
Java

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

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

yes

Triggers

By using transaction functions

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

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

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication
XtraDB Cluster

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

can define user-defined aggregate functions for map-reduce-style calculations

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

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

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Users with fine-grained authorization concept

no user groups or roles

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 control via users, groups and roles

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.