DBMS > OpenQM vs. Qdrant vs. SAP HANA vs. SpatiaLite vs. Vitess

System Properties Comparison OpenQM vs. Qdrant vs. SAP HANA vs. SpatiaLite vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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

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

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

Spatial extension of SQLite

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

Document store
Spatial DBMS

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

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

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/hana.html

www.gaia-gis.it/fossil/libspatialite/index

vitess.io

Technical documentation

qdrant.tech/documentation

help.sap.com/hana

www.gaia-gis.it/gaia-sins/spatialite_topics.html

vitess.io/docs

Developer

Rocket Software, originally Martin Phillips

Qdrant

SAP

Alessandro Furieri

The Linux Foundation, PlanetScale

Initial release

1993

2021

2010

2008

2013

Current release

3.4-12

2.0 SPS07 (April 4, 2023), April 2023

5.0.0, August 2020

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

Open Source

Apache Version 2.0

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 2.0, commercial licenses available

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

Rust

C++

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Docker
Linux
macOS
Windows

Appliance or cloud-service

server-less

Docker
Linux
macOS

Data scheme

yes

with some exceptions

schema-free

yes

Typing

predefined data types such as float or date

Numbers, Strings, Geo, Boolean

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Collection-level replication

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights can be defined down to the item level

Key-based authentication

yes

Users with fine-grained authorization concept

no user groups or roles

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.