DBMS > Qdrant vs. RocksDB

System Properties Comparison Qdrant vs. RocksDB

Please select another system to include it in the comparison.

Our visitors often compare Qdrant and RocksDB with Elasticsearch, MongoDB and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

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

Vector DBMS

Key-value store

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

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	2.84
Rank	#97	Overall
	#16	Key-value stores

Website

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

Technical documentation

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

Developer

Qdrant

Facebook, Inc.

Initial release

2021

2013

Current release

9.4.0, June 2024

License

Commercial or Open Source

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

Rust

C++

Server operating systems

Docker
Linux
macOS
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

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

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

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

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.