DBMS > Cubrid vs. Drizzle vs. Google BigQuery vs. Graph Engine vs. jBASE

System Properties Comparison Cubrid vs. Drizzle vs. Google BigQuery vs. Graph Engine vs. jBASE

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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 robust multi-value DBMS comprising development tools and middleware

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Multivalue DBMS

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

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

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Website

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

cloud.google.com/bigquery

www.graphengine.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

CUBRID Corporation, CUBRID Foundation

Drizzle project, originally started by Brian Aker

Google

Microsoft

Rocket Software (formerly Zumasys)

Initial release

2008

2010

1991

Current release

11.0, January 2021

7.2.4, September 2012

5.7

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

commercial

Open Source

MIT License

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

C++

.NET and C

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X

hosted

.NET

AIX
Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

with proprietary extensions

yes

Embedded SQL for jBASE in BASIC

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

Triggers

yes

hooks for callbacks inside the server can be used.

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

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.