DBMS > H2 vs. Qdrant vs. Redis vs. searchxml

System Properties Comparison H2 vs. Qdrant vs. Redis vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A high-performance vector database with neural network or semantic-based matching

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.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Vector DBMS

Key-value store

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

Native XML DBMS
Search engine

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	7.57
Rank	#47	Overall
	#30	Relational DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

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

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

www.h2database.com

github.com/qdrant/qdrant
qdrant.tech

redis.com
redis.io

www.searchxml.net/category/products

Technical documentation

www.h2database.com/html/main.html

qdrant.tech/documentation

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

www.searchxml.net/support/handouts

Developer

Thomas Mueller

Qdrant

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

informationpartners gmbh

Initial release

2005

2021

2009

2015

Current release

2.2.220, July 2023

7.2.5, May 2024

1.0

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2.0

Open Source

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

commercial

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

Rust

C++

Server operating systems

All OS with a Java VM

Docker
Linux
macOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

with RediSearch module

yes

SQL

Support of SQL

yes

with RediSQL module

APIs and other access methods

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Java

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

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

yes

on the application server

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Collection-level replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

sychronisation to multiple collections

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, tunable 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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

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

User concepts

Access control

fine grained access rights according to SQL-standard

Key-based authentication

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

Domain, group and role-based access control at the document level and for application services

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.