DBMS > Alibaba Cloud Table Store vs. Datomic vs. Firebase Realtime Database vs. Graph Engine vs. Redis

System Properties Comparison Alibaba Cloud Table Store vs. Datomic vs. Firebase Realtime Database vs. Graph Engine vs. Redis

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Wide column store

Relational DBMS

Document store

Graph DBMS
Key-value 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

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	0.24
Rank	#310	Overall
	#12	Wide column stores

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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

Website

www.alibabacloud.com/product/table-store

www.datomic.com

firebase.google.com/products/realtime-database

www.graphengine.io

redis.com
redis.io

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.datomic.com

firebase.google.com/docs/database

www.graphengine.io/docs/manual

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

Developer

Alibaba

Cognitect

Google

acquired by Google 2014

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2012

2010

2009

Current release

1.0.6735, June 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

MIT License

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

Java, Clojure

.NET and C

Server operating systems

hosted

All OS with a Java VM

hosted

.NET

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

yes

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

with RediSearch module

SQL

Support of SQL

with RediSQL module

APIs and other access methods

HTTP API

RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Java
Python

Clojure
Java

Java
JavaScript
Objective-C

C#
C++
F#
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

Server-side scripts

Stored procedures

yes

Transaction Functions

limited functionality with using 'rules'

yes

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

Triggers

By using transaction functions

Callbacks are triggered when data changes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

But extensive use of caching in the application peers

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

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

if the client is offline
Immediate Consistency

if the client is online

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 single-row operations

ACID

yes

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

Durability

Support for making data persistent

yes

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

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 based on subaccounts and tokens

yes, based on authentication and database rules

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.