DBMS > Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. Qdrant vs. Spark SQL

System Properties Comparison Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. Qdrant vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

Relational DBMS

Secondary database models

Vector DBMS

Spatial DBMS

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

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

github.com/qdrant/qdrant
qdrant.tech

spark.apache.org/sql

Technical documentation

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

qdrant.tech/documentation

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Microsoft

Qdrant

Apache Software Foundation

Initial release

2015

2014

2021

2014

Current release

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Rust

Scala

Server operating systems

hosted

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

yes

using Azure authentication

Access rights can be defined down to the item level

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.