DBMS > Google BigQuery vs. Google Cloud Datastore vs. Microsoft Azure Synapse Analytics vs. Realm vs. SAP Advantage Database Server

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. Microsoft Azure Synapse Analytics vs. Realm vs. SAP Advantage Database Server

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

cloud.google.com/bigquery

cloud.google.com/datastore

azure.microsoft.com/services/synapse-analytics

realm.io

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

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

docs.microsoft.com/azure/synapse-analytics

realm.io/docs

Developer

Google

Microsoft

Realm, acquired by MongoDB in May 2019

Sybase, SAP

Initial release

2010

2008

2016

2014

1993

License

Commercial or Open Source

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

C++

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
PHP

.Net
Java

with Android only
Objective-C
React Native
Swift

Delphi
Perl
PHP

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Transact SQL

runs within the applications so server-side scripts are unnecessary

yes

Triggers

Callbacks using the Google Apps Engine

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

In-Memory realm

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)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

fine grained access rights according to SQL-standard

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.