DBMS > Cubrid vs. GeoMesa vs. IBM Db2 vs. Riak TS

System Properties Comparison Cubrid vs. GeoMesa vs. IBM Db2 vs. Riak TS

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.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Time Series DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

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

www.geomesa.org

www.ibm.com/products/db2

Technical documentation

cubrid.org/manuals

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

www.ibm.com/docs/en/db2

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

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

IBM

Open Source, formerly Basho Technologies

Initial release

2008

2014

1983

host version

2015

Current release

11.0, January 2021

4.0.5, February 2024

12.1, October 2016

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

free version is available

Open Source

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

C and C++

Erlang

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

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

yes, limited

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP API
Native Erlang Interface

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

yes

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

only with Windows/Unix/Linux Version

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

yes

with separate tools (MQ, InfoSphere)

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 datasets 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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.

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

Announcing Amazon RDS for Db2 with license through AWS Marketplace | Amazon Web Services
21 May 2024, AWS Blog

IBM Collaborates with AWS to Launch a New Cloud Database Offering, Enabling Customers to Optimize Data ...
27 November 2023, IBM Newsroom

IBM's vintage Db2 database jumps on AWS's cloud bandwagon
29 November 2023, The Register

Precisely Supports Amazon RDS for Db2 Service with Real-Time Data Integration Capabilities
3 April 2024, precisely.com

Precisely says it's smoothing migration of Db2 analytics data to AWS cloud – Blocks and Files
5 April 2024, Blocks & Files

provided by Google News

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page