DBMS > Google BigQuery vs. Graph Engine vs. Hazelcast vs. HBase

System Properties Comparison Google BigQuery vs. Graph Engine vs. Hazelcast vs. HBase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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 widely adopted in-memory data grid

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store

Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

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

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Website

cloud.google.com/bigquery

www.graphengine.io

hazelcast.com

hbase.apache.org

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

hazelcast.org/imdg/docs

hbase.apache.org/book.html

Developer

Google

Microsoft

Hazelcast

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2010

2008

Current release

5.3.6, November 2023

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache version 2

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

.NET and C

Java

Server operating systems

hosted

.NET

All OS with a Java VM

Linux
Unix
Windows

using Cygwin

Data scheme

yes

schema-free

schema-free, schema definition possible

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

yes

Coprocessors in Java

Triggers

yes

Events

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

yes

Replicated Map

Multi-source replication
Source-replica replication

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

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

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

Single row ACID (across millions of columns)

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

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.