DBMS > HEAVY.AI vs. Lovefield vs. Redis vs. XTDB

System Properties Comparison HEAVY.AI vs. Lovefield vs. Redis vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Embeddable relational database for web apps written in pure JavaScript

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 general purpose database with bitemporal SQL and Datalog and graph queries

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

Document store

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.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

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

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

redis.com
redis.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.heavy.ai

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

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

www.xtdb.com/docs

Developer

HEAVY.AI, Inc.

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Juxt Ltd.

Initial release

2016

2014

2009

2019

Current release

5.10, January 2022

2.1.12, February 2017

7.2.4, January 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

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

Open Source

MIT License

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C++ and CUDA

JavaScript

Clojure

Server operating systems

Linux

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

tested with Chrome, Firefox, IE, Safari

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

All OS with a Java 8 (and higher) VM
Linux

Data scheme

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

yes, extensible-data-notation format

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

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

with RediSQL module

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
Thrift
Vega

proprietary protocol

RESP - REdis Serialization Protocol

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

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

Clojure
Java

Server-side scripts

Stored procedures

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

Triggers

Using read-only observers

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes, each node contains all data

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

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

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

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

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.