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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

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

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

Primary database model

Document store
Relational DBMS

Search engine

Vector DBMS

Relational DBMS

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	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.databricks.com

manticoresearch.com

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/hana.html

Technical documentation

docs.databricks.com

manual.manticoresearch.com

qdrant.tech/documentation

help.sap.com/hana

Developer

Databricks

Manticore Software

Qdrant

SAP

Initial release

2013

2017

2021

2010

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Docker
Linux
macOS
Windows

Appliance or cloud-service

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

with Databricks SQL

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Supported programming languages

Python
R
Scala

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

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

Server-side scripts

Stored procedures

user defined functions and aggregates

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

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

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.