DBMS > Blazegraph vs. Couchbase vs. Cubrid vs. HEAVY.AI vs. Riak KV

System Properties Comparison Blazegraph vs. Couchbase vs. Cubrid vs. HEAVY.AI vs. Riak KV

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Distributed, fault tolerant key-value store

Primary database model

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

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Spatial DBMS

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

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

blazegraph.com

www.couchbase.com

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

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

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

Developer

Blazegraph

Couchbase, Inc.

CUBRID Corporation, CUBRID Foundation

HEAVY.AI, Inc.

OpenSource, formerly Basho Technologies

Initial release

2006

2011

2008

2016

2009

Current release

2.1.5, March 2019

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

11.0, January 2021

5.10, January 2022

3.2.0, December 2022

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

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

Java

C, C++, Go and Erlang

C, C++, Java

C++ and CUDA

Erlang

Server operating systems

Linux
OS X
Windows

Linux
Windows

Linux

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

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

SPARQL is used as query language

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
Thrift
Vega

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

All languages supporting JDBC/ODBC/Thrift
Python

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

yes

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Java Stored Procedures

Erlang

Triggers

yes

via the TAP protocol

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

none

Sharding

Round robin

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

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

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

Ephemeral buckets

yes

User concepts

Access control

Security and Authentication via Web Application Container (Tomcat, Jetty)

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

fine grained access rights according to SQL-standard

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.