DBMS > Google BigQuery vs. Microsoft Azure Synapse Analytics vs. Riak KV vs. Rockset

System Properties Comparison Google BigQuery vs. Microsoft Azure Synapse Analytics vs. Riak KV vs. Rockset

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

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

Distributed, fault tolerant key-value store

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document store

Secondary database models

Relational DBMS
Search engine

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

cloud.google.com/bigquery

azure.microsoft.com/services/synapse-analytics

rockset.com

Technical documentation

cloud.google.com/bigquery/docs

docs.microsoft.com/azure/synapse-analytics

www.tiot.jp/riak-docs/riak/kv/latest

docs.rockset.com

Developer

Google

Microsoft

OpenSource, formerly Basho Technologies

Rockset

Initial release

2010

2016

2009

2019

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

C++

Server operating systems

hosted

Linux
OS X

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

restricted

all fields are automatically indexed

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
PHP

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

no "single point of failure"

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

links between data sets can be stored

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

yes, using Riak Security

Access rights for users and organizations can be defined via Rockset console

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.