DBMS > Google BigQuery vs. Hazelcast vs. SAP Advantage Database Server vs. YDB

System Properties Comparison Google BigQuery vs. Hazelcast vs. SAP Advantage Database Server vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Low-cost RDBMS with access to ISAM and FoxPro data structures

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

cloud.google.com/bigquery

hazelcast.com

www.sap.com/products/advantage-database-server.html

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

ydb.tech/en/docs

Developer

Google

Hazelcast

Sybase, SAP

Yandex

Initial release

2010

2008

1993

2019

Current release

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0; commercial license 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

Java

Server operating systems

hosted

All OS with a Java VM

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Delphi
Perl
PHP

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Active-passive shard 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

Foreign keys

Referential integrity

yes

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

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

caching of (temporary) tables can be configured

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

fine grained access rights according to SQL-standard

Access rights defined for Yandex Cloud users

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.