DBMS > atoti vs. Couchbase vs. GeoMesa vs. Qdrant

System Properties Comparison atoti vs. Couchbase vs. GeoMesa vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

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

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

atoti.io

www.couchbase.com

www.geomesa.org

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.atoti.io

docs.couchbase.com

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

qdrant.tech/documentation

Developer

ActiveViam

Couchbase, Inc.

CCRi and others

Qdrant

Initial release

2011

2014

2021

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

5.0.0, May 2024

License

Commercial or Open Source

commercial

free versions available

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C, C++, Go and Erlang

Scala

Rust

Server operating systems

Linux
OS X
Windows

Docker
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

Multidimensional Expressions (MDX)

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

Python

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Automatic Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

depending on storage layer

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

depending on storage layer

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

Ephemeral buckets

depending on storage layer

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

yes

depending on the DBMS used for storage

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.