DBMS > Brytlyt vs. Google BigQuery vs. Hazelcast vs. IBM Db2

System Properties Comparison Brytlyt vs. Google BigQuery vs. Hazelcast vs. IBM Db2

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Common in IBM host environments, 2 different versions for host and Windows/Linux

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Website

brytlyt.io

cloud.google.com/bigquery

hazelcast.com

www.ibm.com/products/db2

Technical documentation

docs.brytlyt.io

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

www.ibm.com/docs/en/db2

Developer

Brytlyt

Google

Hazelcast

IBM

Initial release

2016

2010

2008

1983

host version

Current release

5.0, August 2023

5.3.6, November 2023

12.1, October 2016

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

free version is 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

Java

C and C++

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Data scheme

yes

schema-free

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

yes

with separate tools (MQ, InfoSphere)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control

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.