DBMS > BoltDB vs. H2 vs. HyperSQL vs. LevelDB vs. Redis

System Properties Comparison BoltDB vs. H2 vs. HyperSQL vs. LevelDB vs. Redis

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Key-value store

Relational DBMS

Key-value store

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

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	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

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

Website

github.com/boltdb/bolt

www.h2database.com

hsqldb.org

github.com/google/leveldb

redis.com
redis.io

Technical documentation

www.h2database.com/html/main.html

hsqldb.org/web/hsqlDocsFrame.html

github.com/google/leveldb/blob/main/doc/index.md

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

Developer

Thomas Mueller

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2013

2005

2001

2011

2009

Current release

2.2.220, July 2023

2.7.2, June 2023

1.23, February 2021

7.2.4, January 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

based on BSD license

Open Source

BSD

Open Source

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

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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Illumos
Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

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.

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

with RediSQL module

APIs and other access methods

JDBC
ODBC

HTTP API

JDBC via HTTP
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Java

All languages supporting JDBC/ODBC
Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Java Stored Procedures and User-Defined Functions

Java, SQL

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

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

With clustering: 2 database servers on different computers operate on identical copies of a database

none

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

none

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

yes

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with automatic compression on writes

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

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.