DBMS > Cubrid vs. Galaxybase vs. Google BigQuery vs. Graph Engine vs. JaguarDB

System Properties Comparison Cubrid vs. Galaxybase vs. Google BigQuery vs. Graph Engine vs. JaguarDB

Editorial information provided by DB-Engines

Name

Description

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

Scalable, ACID-compliant native distributed parallel graph platform

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Graph DBMS
Key-value store

Key-value store
Vector DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

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

galaxybase.com

cloud.google.com/bigquery

www.graphengine.io

www.jaguardb.com

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

www.jaguardb.com/support.html

Developer

CUBRID Corporation, CUBRID Foundation

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Google

Microsoft

DataJaguar, Inc.

Initial release

2008

2017

2010

2015

Current release

11.0, January 2021

Nov 20, November 2021

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Open Source

GPL V3.0

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

C and Java

.NET and C

C++

the server part. Clients available in other languages

Server operating systems

Linux
Windows

Linux

hosted

.NET

Linux

Data scheme

yes

Strong typed schema

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

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

Go
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

Java Stored Procedures

user defined procedures and functions

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

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.