DBMS > Cubrid vs. GeoMesa vs. Qdrant vs. Riak KV

System Properties Comparison Cubrid vs. GeoMesa vs. Qdrant vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.23
Rank	#171	Overall
	#6	Vector DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

cubrid.com (korean)
cubrid.org (english)

www.geomesa.org

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

cubrid.org/manuals

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

qdrant.tech/documentation

www.tiot.jp/riak-docs/riak/kv/latest

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

Qdrant

OpenSource, formerly Basho Technologies

Initial release

2008

2014

2021

2009

Current release

11.0, January 2021

4.0.5, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

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

C, C++, Java

Scala

Rust

Erlang

Server operating systems

Linux
Windows

Docker
Linux
macOS
Windows

Linux
OS X

Data scheme

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

Collection-level replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency, tunable consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Key-based authentication

yes, using Riak Security

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

Recent citations in the news

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

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

Qdrant launches first vector database as a managed hybrid cloud
16 April 2024, VentureBeat

Open-source vector database Qdrant launches hybrid cloud for enterprise AI apps
16 April 2024, SiliconANGLE News

Qdrant Announces an Industry-First Hybrid Cloud Offering For Enterprise AI Applications
16 April 2024, Yahoo Finance

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page