DBMS > Lovefield vs. OpenQM vs. Redis vs. YDB

System Properties Comparison Lovefield vs. OpenQM vs. Redis vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

QpenQM is a high-performance, self-tuning, multi-value DBMS

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 distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Multivalue DBMS

Key-value store

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

Document store
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

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

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

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

Score	0.39
Rank	#269	Overall
	#43	Document stores
	#126	Relational DBMS

Website

google.github.io/lovefield

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

redis.com
redis.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

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

ydb.tech/en/docs

Developer

Google

Rocket Software, originally Martin Phillips

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Yandex

Initial release

2014

1993

2009

2019

Current release

2.1.12, February 2017

3.4-12

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

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

Open Source

Apache 2.0; commercial license 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

JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

yes

with some exceptions

schema-free

Flexible Schema (defined schema, partial schema, 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

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

SQL-like query language

via JavaScript builder pattern

with RediSQL module

SQL-like query language (YQL)

APIs and other access methods

proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

JavaScript

.Net
Basic
C
Java
Objective C
PHP
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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

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

Triggers

Using read-only observers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Active-passive shard replication

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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 MemoryDB

yes

User concepts

Access control

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

Access rights defined for Yandex Cloud users

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.