DBMS > GBase vs. IBM Cloudant vs. JanusGraph vs. Kinetica vs. MySQL

System Properties Comparison GBase vs. IBM Cloudant vs. JanusGraph vs. Kinetica vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Database as a Service offering based on Apache CouchDB

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Fully vectorized database across both GPUs and CPUs

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

www.gbase.cn

www.ibm.com/products/cloudant

janusgraph.org

www.kinetica.com

www.mysql.com

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.janusgraph.org

docs.kinetica.com

dev.mysql.com/doc

Developer

General Data Technology Co., Ltd.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Linux Foundation; originally developed as Titan by Aurelius

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2004

2010

2017

2012

1995

Current release

GBase 8a, GBase 8s, GBase 8c

0.6.3, February 2023

7.1, August 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, Java, Python

Erlang

Java

C, C++

C and C++

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Clojure
Java
Python

C++
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

View functions (Map-Reduce) in JavaScript

yes

user defined functions

yes

proprietary syntax

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

User concepts

Access control

yes

Access rights for users can be defined per database

User authentification and security via Rexster Graph Server

Access rights for users and roles on table level

Users with fine-grained authorization concept

no user groups or roles

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.