DBMS > Cachelot.io vs. Cubrid vs. Google BigQuery vs. Riak TS vs. TigerGraph

System Properties Comparison Cachelot.io vs. Cubrid vs. Google BigQuery vs. Riak TS vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Large scale data warehouse service with append-only tables

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

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

Primary database model

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

cachelot.io

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

cloud.google.com/bigquery

www.tigergraph.com

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

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

docs.tigergraph.com

Developer

CUBRID Corporation, CUBRID Foundation

Google

Open Source, formerly Basho Technologies

Initial release

2015

2008

2010

2015

2017

Current release

11.0, January 2021

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache Version 2.0

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C, C++, Java

Erlang

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

hosted

Linux
OS X

Linux

Data scheme

schema-free

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

yes, limited

SQL-like query language (GSQL)

APIs and other access methods

Memcached protocol

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

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

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

.Net
Java
JavaScript
Objective-C
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

user defined functions

in JavaScript

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying 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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.