DBMS > Machbase Neo vs. Microsoft Azure Cosmos DB vs. Qdrant vs. SiriDB

System Properties Comparison Machbase Neo vs. Microsoft Azure Cosmos DB vs. Qdrant vs. SiriDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

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

Open Source Time Series DBMS

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

machbase.com

azure.microsoft.com/services/cosmos-db

github.com/qdrant/qdrant
qdrant.tech

siridb.com

Technical documentation

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

qdrant.tech/documentation

docs.siridb.com

Developer

Machbase

Microsoft

Qdrant

Cesbit

Initial release

2013

2014

2021

2017

Current release

V8.0, August 2023

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

Apache Version 2.0

Open Source

MIT License

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

Server operating systems

Linux
macOS
Windows

hosted

Docker
Linux
macOS
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

Numbers, Strings, Geo, Boolean

yes

Numeric data

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

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

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

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

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

Collection-level replication

yes

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

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

volatile and lookup table

yes

User concepts

Access control

simple password-based access control

Access rights can be defined down to the item level

Key-based authentication

simple rights management via user accounts

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.