DBMS > Amazon DynamoDB vs. DataFS vs. Google Cloud Datastore vs. TempoIQ

System Properties Comparison Amazon DynamoDB vs. DataFS vs. Google Cloud Datastore vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Key-value store

Object oriented DBMS

Document store

Time Series DBMS

Secondary database models

Graph DBMS

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

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

aws.amazon.com/dynamodb

newdatabase.com

cloud.google.com/datastore

tempoiq.com (offline)

Technical documentation

docs.aws.amazon.com/dynamodb

dev.mobiland.com/Overview.xsp

cloud.google.com/datastore/docs

Developer

Amazon

Mobiland AG

Google

TempoIQ

Initial release

2012

2018

2008

2012

Current release

1.1.263, October 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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.

Server operating systems

hosted

Windows

hosted

Data scheme

schema-free

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

APIs and other access methods

RESTful HTTP API

.NET Client API
Proprietary client DLL
WinRT client

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

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C#
C++
VB.Net

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

by integration with AWS Lambda

no, except callback-events from server when changes happened

Callbacks using the Google Apps Engine

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

Proprietary Sharding system

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

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

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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

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.

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Windows-Profile

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

simple authentication-based access control

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.