DBMS > Cubrid vs. Dgraph vs. GeoMesa vs. Riak TS

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

Distributed and scalable native Graph DBMS

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

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

Primary database model

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

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

dgraph.io

www.geomesa.org

Technical documentation

cubrid.org/manuals

dgraph.io/docs

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

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

Developer

CUBRID Corporation, CUBRID Foundation

Dgraph Labs, Inc.

CCRi and others

Open Source, formerly Basho Technologies

Initial release

2008

2016

2014

2015

Current release

11.0, January 2021

4.0.5, February 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache License 2.0

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

Erlang

Server operating systems

Linux
Windows

Linux
OS X
Windows

Linux
OS X

Data scheme

yes

schema-free

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
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

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

yes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication via Raft

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

Planned for future releases

yes

depending on the DBMS used for storage

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

Dgraph on AWS: Setting up a horizontally scalable graph database | Amazon Web Services
1 September 2020, AWS Blog

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

Dgraph Rises to the Top Graph Database on GitHub With 11 G2 Badges and 11M Downloads
26 May 2021, Business Wire

Dgraph Raises $6M in Seed Funding
20 July 2022, FinSMEs

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