DBMS > Google Cloud Datastore vs. Graph Engine vs. SAP SQL Anywhere vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. Graph Engine vs. SAP SQL Anywhere 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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Document store

Graph DBMS
Key-value store

Relational DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cloud.google.com/datastore

www.graphengine.io

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

Technical documentation

cloud.google.com/datastore/docs

www.graphengine.io/docs/manual

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

Developer

Google

Microsoft

SAP

formerly Sybase

Snowflake Computing Inc.

Initial release

2008

2010

1992

2014

Current release

17, July 2015

License

Commercial or Open Source

commercial

Open Source

MIT License

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

.NET and C

Server operating systems

hosted

.NET

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

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

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

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

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

yes, in C/C++, Java, .Net or Perl

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Database mirroring

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.