DBMS > Amazon DynamoDB vs. Geode vs. Google Cloud Datastore vs. IBM Db2 warehouse vs. SAP SQL Anywhere

System Properties Comparison Amazon DynamoDB vs. Geode vs. Google Cloud Datastore vs. IBM Db2 warehouse vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Cloud-based data warehousing service

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

Primary database model

Document store
Key-value store

Key-value store

Document store

Relational DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

aws.amazon.com/dynamodb

geode.apache.org

cloud.google.com/datastore

www.ibm.com/products/db2/warehouse

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

Technical documentation

docs.aws.amazon.com/dynamodb

geode.apache.org/docs

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

IBM

SAP

formerly Sybase

Initial release

2012

2002

2008

2014

1992

Current release

1.1, February 2017

17, July 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

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

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

PL/SQL, SQL PL

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

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication using Paxos

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual 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

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes, on a single node

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

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights per client and object definable

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

fine grained access rights according to SQL-standard

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.