DBMS > Bangdb vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Graphite

System Properties Comparison Bangdb vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Graphite

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Website

bangdb.com

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

cloud.google.com/bigquery

www.graphengine.io

github.com/graphite-project/graphite-web

Technical documentation

docs.bangdb.com

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

graphite.readthedocs.io

Developer

Sachin Sinha, BangDB

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Chris Davis

Initial release

2012

2008

2010

2006

Current release

BangDB 2.0, October 2021

11.0, January 2021

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Open Source

Apache 2.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++

C, C++, Java

.NET and C

Python

Server operating systems

Linux

Linux
Windows

hosted

.NET

Linux
Unix

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes

Numeric data only

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

HTTP API
Sockets

Supported programming languages

C
C#
C++
Java
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

none

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

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

locking

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

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, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

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.