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

System Properties Comparison Cubrid vs. DuckDB vs. GeoMesa 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

An embeddable, in-process, column-oriented SQL OLAP RDBMS

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

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

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	4.68
Rank	#76	Overall
	#41	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

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

Website

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

duckdb.org

www.geomesa.org

Technical documentation

cubrid.org/manuals

duckdb.org/docs

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

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

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

OpenSource, formerly Basho Technologies

Initial release

2008

2018

2014

2009

Current release

11.0, January 2021

0.10, February 2024

4.0.5, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

Apache License 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

C++

Scala

Erlang

Server operating systems

Linux
Windows

server-less

Linux
OS X

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

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

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

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

none

depending on storage layer

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

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

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

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

DuckDB Walks to the Beat of Its Own Analytics Drum
5 March 2024, Datanami

Enabling Remote Query Execution through DuckDB Extensions
12 March 2024, InfoQ.com

How to read OSM data with DuckDB | Kamil Raczycki
1 March 2024, Towards Data Science

Seattle startup MotherDuck raises $52.5M at a $400M valuation to fuel DuckDB analytics platform
20 September 2023, GeekWire

MotherDuck Raises $52.5 Million Series B Funding as DuckDB Adoption Soars
20 September 2023, PR Newswire

provided by Google News

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

Photos: Woodstock music graduate Alex Riak returns to work with students
11 December 2023, Shaw Local News Network

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

provided by Google News

Share this page