DBMS > Google BigQuery vs. Hazelcast vs. Microsoft Azure SQL Database vs. Percona Server for MongoDB

System Properties Comparison Google BigQuery vs. Hazelcast vs. Microsoft Azure SQL Database vs. Percona Server for MongoDB

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

Database as a Service offering with high compatibility to Microsoft SQL Server

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS

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	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Website

cloud.google.com/bigquery

hazelcast.com

azure.microsoft.com/en-us/products/azure-sql/database

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

docs.microsoft.com/en-us/azure/azure-sql

docs.percona.com/percona-distribution-for-mongodb

Developer

Google

Hazelcast

Microsoft

Percona

Initial release

2010

2008

2010

2015

Current release

5.3.6, November 2023

V12

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL 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

Java

C++

Server operating systems

hosted

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

yes

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Transact SQL

JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes, with always 3 replicas available

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

Eventual Consistency
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

via In-Memory Engine

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 for users and roles

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.