DBMS > Google Cloud Datastore vs. Microsoft Access vs. Quasardb vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. Microsoft Access vs. Quasardb vs. Snowflake

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Distributed, high-performance timeseries database

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

Primary database model

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cloud.google.com/datastore

www.microsoft.com/en-us/microsoft-365/access

quasar.ai

www.snowflake.com

Technical documentation

cloud.google.com/datastore/docs

developer.microsoft.com/en-us/access

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

Developer

Google

Microsoft

quasardb

Snowflake Computing Inc.

Initial release

2008

1992

2009

2014

Current release

1902 (16.0.11328.20222), March 2019

3.14.1, January 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Windows

Not a real database server, but making use of DLLs

BSD
Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes, details here

yes

integer and binary

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

with tags

SQL

Support of SQL

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

SQL-like query language

yes

APIs and other access methods

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

ADO.NET
DAO
ODBC
OLE DB

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

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

a simple user-level security was built in till version Access 2003

Cryptographically strong user authentication and audit trail

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.