DBMS > Cubrid vs. Google BigQuery vs. Graph Engine vs. MonetDB vs. Transwarp Hippo

System Properties Comparison Cubrid vs. Google BigQuery vs. Graph Engine vs. MonetDB vs. Transwarp Hippo

Editorial information provided by DB-Engines

Name

Description

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

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

A relational database management system that stores data in columns

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Vector DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

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

cloud.google.com/bigquery

www.graphengine.io

www.monetdb.org

www.transwarp.cn/en/subproduct/hippo

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

www.monetdb.org/Documentation

Developer

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

MonetDB BV

Initial release

2008

2010

2004

2023

Current release

11.0, January 2021

Dec2023 (11.49), December 2023

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Open Source

Mozilla Public License 2.0

commercial

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

.NET and C

C++

Server operating systems

Linux
Windows

hosted

.NET

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

SQL 2003 with some extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

RESTful HTTP API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

C++
Java
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

yes, in SQL, C, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding via remote tables

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication available in experimental status

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

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

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Role based access control and fine grained access rights

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.