DBMS > Qdrant vs. SAP HANA vs. Solr vs. WakandaDB

System Properties Comparison Qdrant vs. SAP HANA vs. Solr vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A widely used distributed, scalable search engine based on Apache Lucene

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/hana.html

solr.apache.org

wakanda.github.io

Technical documentation

qdrant.tech/documentation

help.sap.com/hana

solr.apache.org/resources.html

wakanda.github.io/doc

Developer

Qdrant

SAP

Apache Software Foundation

Wakanda SAS

Initial release

2021

2010

2006

2012

Current release

2.0 SPS07 (April 4, 2023), April 2023

9.6.1, May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2

Open Source

AGPLv3, extended commercial license 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

Java

C++, JavaScript

Server operating systems

Docker
Linux
macOS
Windows

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
OS X
Windows

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

Numbers, Strings, Geo, Boolean

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

SQLScript, R

Java plugins

yes

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Collection-level replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

ACID

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

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.