DBMS > GeoMesa vs. Qdrant vs. RethinkDB vs. ToroDB

System Properties Comparison GeoMesa vs. Qdrant vs. RethinkDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Spatial DBMS

Vector DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Website

www.geomesa.org

github.com/qdrant/qdrant
qdrant.tech

rethinkdb.com

github.com/torodb/server

Technical documentation

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

qdrant.tech/documentation

rethinkdb.com/docs

Developer

CCRi and others

Qdrant

The Linux Foundation

since July 2017

8Kdata

Initial release

2014

2021

2009

2016

Current release

5.0.0, May 2024

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2

Open Source

AGPL-V3

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

Scala

Rust

C++

Java

Server operating systems

Docker
Linux
macOS
Windows

Linux
OS X
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

string, binary, float, bool, date, geometry

yes

string, integer, double, boolean, date, object_id

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

yes

SQL

Support of SQL

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

Triggers

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

range based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Collection-level replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

Key-based authentication

yes

users and table-level permissions

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Meet some database management systems you are likely to hear more about in the future
4 August 2014, Paul Andlinger

show all

Recent citations in the news

Open source vector database startup Qdrant raises $28M
23 January 2024, TechCrunch

Qdrant Raises $28M to Advance Massive-Scale AI Applications
23 January 2024, businesswire.com

Qdrant Hybrid Cloud is Now Available for OCI Customers: Managed Vector Search Engine for Data-Sensitive AI ...
16 April 2024, blogs.oracle.com

Qdrant offers managed vector database for hybrid clouds
16 April 2024, InfoWorld

Why Vector Data Services For AI Are A Moveable Feast
17 April 2024, Forbes

provided by Google News

An introduction to building realtime apps with RethinkDB
9 July 2022, devmio

How to Use RethinkDB with Node.js Applications — SitePoint
16 December 2015, SitePoint

Stripe acquires team behind NoSQL database startup RethinkDB
5 October 2016, VentureBeat

RethinkDB is dead, and MongoDB isn't what killed it
24 January 2017, TechRepublic

Open Source Horizon Claims Edge over Google's Firebase Mobile Back-End -- ADTmag
23 May 2016, ADT Magazine

provided by Google News

Share this page