DBMS > Amazon Aurora vs. Google Cloud Datastore vs. OrigoDB vs. Snowflake

System Properties Comparison Amazon Aurora vs. Google Cloud Datastore vs. OrigoDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

A fully ACID in-memory object graph database

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

Primary database model

Relational DBMS

Document store

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

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

Score	7.84
Rank	#44	Overall
	#28	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

aws.amazon.com/rds/aurora

cloud.google.com/datastore

origodb.com

www.snowflake.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

cloud.google.com/datastore/docs

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Amazon

Google

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2015

2008

2009

under the name LiveDB

2014

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

Server operating systems

hosted

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

yes, details here

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

using Google App Engine

yes

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

Source-replica replication

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

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

depending on model

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

Write ahead log

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

fine grained access rights according to SQL-standard

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

Role based authorization

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.