DBMS > Google BigQuery vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. SQream DB

System Properties Comparison Google BigQuery vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. SQream DB

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

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

sqream.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.sqream.com

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

SQream Technologies

Initial release

2010

2014

2017

Current release

2022.1.6, December 2022

License

Commercial or 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

Erlang

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes, ANSI Standard SQL Types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.Net
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

JavaScript

user defined functions in Python

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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)

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.