DBMS > Manticore Search vs. Qdrant vs. Quasardb vs. SAP HANA

System Properties Comparison Manticore Search vs. Qdrant vs. Quasardb vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-storage database for search, including full-text search.

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

Distributed, high-performance timeseries database

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

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

manticoresearch.com

github.com/qdrant/qdrant
qdrant.tech

quasar.ai

www.sap.com/products/hana.html

Technical documentation

manual.manticoresearch.com

qdrant.tech/documentation

doc.quasar.ai/master

help.sap.com/hana

Developer

Manticore Software

Qdrant

quasardb

SAP

Initial release

2017

2021

2009

2010

Current release

6.0, February 2023

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

Apache Version 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

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++

Server operating systems

FreeBSD
Linux
macOS
Windows

Docker
Linux
macOS
Windows

BSD
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

Numbers, Strings, Geo, Boolean

yes

integer and binary

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

Keywords, numberic ranges, geo, full-text

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API

JDBC
ODBC

Supported programming languages

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Collection-level replication

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Key-based authentication

Cryptographically strong user authentication and audit trail

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.