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

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

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.

Distributed, fault tolerant key-value store

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

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

Graph DBMS

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	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

www.geomesa.org

www.tigergraph.com

Technical documentation

cubrid.org/manuals

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

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

docs.tigergraph.com

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

OpenSource, formerly Basho Technologies

Initial release

2008

2014

2009

2017

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, commercial enterprise edition

commercial

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

Erlang

C++

Server operating systems

Linux
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

yes

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

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Native Erlang Interface

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

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

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

yes

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

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

yes

Relationships in graphs

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

yes, using Riak Security

Role-based access control

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

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

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

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

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

TigerGraph Unveils CoPilot, Version 4.0, and New CEO
30 April 2024, Datanami

How TigerGraph CoPilot enables graph-augmented AI
30 April 2024, InfoWorld

TigerGraph unveils GenAI assistant, introduces new CEO
30 April 2024, TechTarget

TigerGraph Bolsters DB for Enterprise Graph Workloads
1 November 2023, Datanami

Aerospike takes on Neo4j and TigerGraph with launch of graph database
20 June 2023, SiliconANGLE News

provided by Google News

Share this page