DBMS > Google BigQuery vs. Graph Engine vs. Microsoft Azure Synapse Analytics vs. OpenMLDB vs. Snowflake

System Properties Comparison Google BigQuery vs. Graph Engine vs. Microsoft Azure Synapse Analytics vs. OpenMLDB vs. Snowflake

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

An open-source machine learning database that provides a feature platform for training and inference

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	0.02
Rank	#367	Overall
	#37	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cloud.google.com/bigquery

www.graphengine.io

azure.microsoft.com/services/synapse-analytics

openmldb.ai

www.snowflake.com

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.microsoft.com/azure/synapse-analytics

openmldb.ai/docs/zh/main

docs.snowflake.net/manuals/index.html

Developer

Google

Microsoft

4 Paradigm Inc.

Snowflake Computing Inc.

Initial release

2010

2016

2020

2014

Current release

2024-2 February 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

commercial

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

C++

C++, Java, Scala

Server operating systems

hosted

.NET

hosted

Linux

hosted

Data scheme

yes

Fixed schema

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
JDBC
ODBC

JDBC
SQLAlchemy

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C#
Java
PHP

C++
Go
Java
Python
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Transact SQL

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding, horizontal partitioning

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

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)

yes

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.