DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. Qdrant vs. Yaacomo

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. Qdrant vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Globally distributed, horizontally scalable, multi-model database service

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial 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

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

github.com/qdrant/qdrant
qdrant.tech

yaacomo.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

learn.microsoft.com/azure/cosmos-db

qdrant.tech/documentation

Developer

CCRi and others

Microsoft

Qdrant

Q2WEB GmbH

Initial release

2014

2021

2009

Current release

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

commercial

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

Scala

Rust

Server operating systems

hosted

Docker
Linux
macOS
Windows

Android
Linux
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

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

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

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

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

Collection-level replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Multi-item ACID transactions with snapshot isolation within a partition

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

Key-based authentication

fine grained access rights according to SQL-standard

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.