DBMS > Cubrid vs. MySQL vs. SAP HANA vs. Tarantool vs. Titan

System Properties Comparison Cubrid vs. MySQL vs. SAP HANA vs. Tarantool vs. Titan

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

Widely used open source RDBMS

In-memory, column based data store. Available as appliance or cloud service

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

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

www.mysql.com

www.sap.com/products/hana.html

www.tarantool.io

github.com/thinkaurelius/titan

Technical documentation

cubrid.org/manuals

dev.mysql.com/doc

help.sap.com/hana

www.tarantool.io/en/doc

github.com/thinkaurelius/titan/wiki

Developer

CUBRID Corporation, CUBRID Foundation

Oracle

since 2010, originally MySQL AB, then Sun

SAP

Aurelius, owned by DataStax

Initial release

2008

1995

2010

2008

2012

Current release

11.0, January 2021

8.4.0, April 2024

2.0 SPS07 (April 4, 2023), April 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache license, version 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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, C++, Java

C and C++

Java

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

BSD
Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Open binary protocol

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Clojure
Java
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

SQLScript, R

Lua, C and SQL stored procedures

yes

Triggers

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

yes

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graph

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

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

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

User authentification and security via Rexster Graph Server

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.