DBMS > Cubrid vs. FoundationDB vs. Google BigQuery vs. Graph Engine

System Properties Comparison Cubrid vs. FoundationDB vs. Google BigQuery vs. Graph Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

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

Ordered key-value store. Core features are complimented by layers.

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

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Graph DBMS
Key-value store

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

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

Website

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

github.com/apple/foundationdb

cloud.google.com/bigquery

www.graphengine.io

Technical documentation

cubrid.org/manuals

apple.github.io/foundationdb

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

Developer

CUBRID Corporation, CUBRID Foundation

FoundationDB

Google

Microsoft

Initial release

2008

2013

2010

Current release

11.0, January 2021

6.2.28, November 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

MIT License

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

.NET and C

Server operating systems

Linux
Windows

Linux
OS X
Windows

hosted

.NET

Data scheme

yes

schema-free

some layers support schemas

yes

Typing

predefined data types such as float or date

yes

some layers support typing

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

supported in specific SQL layer only

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

Java Stored Procedures

in SQL-layer only

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

in SQL-layer only

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

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)

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.