DBMS > Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. QuestDB

System Properties Comparison Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

A high performance open source SQL database for time series data

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	5.34
Rank	#76	Overall
	#12	Document stores

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

Score	2.31
Rank	#137	Overall
	#10	Time Series DBMS

Website

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

questdb.io

Technical documentation

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

questdb.io/docs

Developer

Google

Microsoft

QuestDB Technology Inc

Initial release

2008

2014

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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 (Zero-GC), C++, Rust

Server operating systems

hosted

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes, details here

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

SQL with time-series extensions

APIs and other access methods

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

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

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

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

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Triggers

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

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

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB Release Week #4
24 November 2023

Building a faster hash table for high performance SQL joins
23 November 2023

Is all data time series data?
21 November 2023

Solving duplicate data with performant deduplication
16 November 2023

QuestDB + Hacktoberfest 2023: 10 Years of Hacking
3 October 2023

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.