DBMS > Atos Standard Common Repository vs. Cubrid vs. Quasardb vs. RocksDB vs. TigerGraph

System Properties Comparison Atos Standard Common Repository vs. Cubrid vs. Quasardb vs. RocksDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Distributed, high-performance timeseries database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Primary database model

Document store
Key-value store

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

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

quasar.ai

rocksdb.org

www.tigergraph.com

Technical documentation

cubrid.org/manuals

doc.quasar.ai/master

github.com/facebook/rocksdb/wiki

docs.tigergraph.com

Developer

Atos Convergence Creators

CUBRID Corporation, CUBRID Foundation

quasardb

Facebook, Inc.

Initial release

2016

2008

2009

2013

2017

Current release

1703

11.0, January 2021

3.14.1, January 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

BSD

commercial

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

C++

Server operating systems

Linux

Linux
Windows

BSD
Linux
OS X
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
OLE DB

HTTP API

C++ API
Java API

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

Supported programming languages

All languages with LDAP bindings

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

consistent hashing

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.