DBMS > Amazon DynamoDB vs. Google Cloud Datastore vs. InterSystems IRIS vs. Riak KV

System Properties Comparison Amazon DynamoDB vs. Google Cloud Datastore vs. InterSystems IRIS vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A containerised multi-model DBMS, interoperability and analytics data platform with wide capabilities for vertical and horizontal scalability

Distributed, fault tolerant key-value store

Primary database model

Document store
Key-value store

Document store

Document store
Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.54
Rank	#84	Overall
	#14	Document stores
	#10	Key-value stores
	#1	Object oriented DBMS
	#45	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.intersystems.com/products/intersystems-iris

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon

Google

InterSystems

OpenSource, formerly Basho Technologies

Initial release

2012

2008

2018

2009

Current release

2023.3, June 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

AIX
Linux
macOS
Ubuntu
Windows

Linux
OS X

Data scheme

schema-free

depending on used data model

schema-free

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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C++
Java
JavaScript (Node.js)
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

using Google App Engine

yes

Erlang

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

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

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

links between data sets can be stored

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

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

yes, using Riak Security

More information provided by the system vendor

Specific characteristics

InterSystems IRIS is a complete cloud-first data platform which includes a multi-model...
» more

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.