DBMS > Cubrid vs. Google Cloud Datastore vs. MonetDB vs. MySQL

System Properties Comparison Cubrid vs. Google Cloud Datastore vs. MonetDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A relational database management system that stores data in columns

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1.72
Rank	#135	Overall
	#62	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

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

cloud.google.com/datastore

www.monetdb.org

www.mysql.com

Technical documentation

cubrid.org/manuals

cloud.google.com/datastore/docs

www.monetdb.org/Documentation

dev.mysql.com/doc

Developer

CUBRID Corporation, CUBRID Foundation

Google

MonetDB BV

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2004

1995

Current release

11.0, January 2021

Dec2023 (11.49), December 2023

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla Public License 2.0

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.

Implementation language

C, C++, Java

C and C++

Server operating systems

Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

SQL 2003 with some extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

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

Java Stored Procedures

using Google App Engine

yes, in SQL, C, R

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding via remote tables

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.