DBMS > H2GIS vs. Qdrant vs. RocksDB

System Properties Comparison H2GIS vs. Qdrant vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Spatial DBMS

Vector DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.h2gis.org

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

Technical documentation

www.h2gis.org/docs/home

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

Developer

CNRS

Qdrant

Facebook, Inc.

Initial release

2013

2021

2013

Current release

9.2.1, May 2024

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

Apache Version 2.0

Open Source

BSD

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

Docker
Linux
macOS
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

SQL

Support of SQL

yes

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

Supported programming languages

Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

based on H2

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Collection-level replication

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

yes

based on H2

Key-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.