DBMS > Brytlyt vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. IBM Db2 Event Store

System Properties Comparison Brytlyt vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. IBM Db2 Event Store

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

Distributed Event Store optimized for Internet of Things use cases

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Event Store
Time Series DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

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	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Website

brytlyt.io

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

cloud.google.com/bigquery

www.graphengine.io

www.ibm.com/products/db2-event-store

Technical documentation

docs.brytlyt.io

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

www.ibm.com/docs/en/db2-event-store

Developer

Brytlyt

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

IBM

Initial release

2016

2008

2010

2017

Current release

5.0, August 2023

11.0, January 2021

2.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

commercial

free developer edition 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++ and CUDA

C, C++, Java

.NET and C

C and C++

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

.NET

Linux

Linux, macOS, Windows for the developer addition

Data scheme

yes

Typing

predefined data types such as float or date

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Java Stored Procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Active-active shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

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 - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared 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)

fine grained access rights according to SQL-standard

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.