DBMS > Drizzle vs. Qdrant vs. RethinkDB vs. SAP HANA vs. SwayDB

System Properties Comparison Drizzle vs. Qdrant vs. RethinkDB vs. SAP HANA vs. SwayDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

In-memory, column based data store. Available as appliance or cloud service

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

github.com/qdrant/qdrant
qdrant.tech

rethinkdb.com

www.sap.com/products/hana.html

swaydb.simer.au

Technical documentation

qdrant.tech/documentation

rethinkdb.com/docs

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

Qdrant

The Linux Foundation

since July 2017

SAP

Simer Plaha

Initial release

2008

2021

2009

2010

2018

Current release

7.2.4, September 2012

2.4.1, August 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2.0

Open Source

Apache Version 2

commercial

Open Source

GNU Affero GPL V3.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Rust

C++

Scala

Server operating systems

FreeBSD
Linux
OS X

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

string, binary, float, bool, date, geometry

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.

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Java
Kotlin
Scala

Server-side scripts

Stored procedures

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic single-document operations

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Key-based authentication

yes

users and table-level permissions

yes

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.