DBMS > Amazon DynamoDB vs. Datomic vs. FatDB vs. Google Cloud Datastore vs. SAP SQL Anywhere

System Properties Comparison Amazon DynamoDB vs. Datomic vs. FatDB vs. Google Cloud Datastore vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Primary database model

Document store
Key-value store

Relational DBMS

Document 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.66
Rank	#144	Overall
	#66	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

aws.amazon.com/dynamodb

www.datomic.com

cloud.google.com/datastore

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

Technical documentation

docs.aws.amazon.com/dynamodb

docs.datomic.com

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon

Cognitect

FatCloud

Google

SAP

formerly Sybase

Initial release

2012

2008

1992

Current release

1.0.7075, December 2023

17, July 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

limited edition free

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

Server operating systems

hosted

All OS with a Java VM

Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
Java

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

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

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

via applications

using Google App Engine

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

Triggers

yes

by integration with AWS Lambda

By using transaction functions

yes

via applications

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

selectable replication factor

Multi-source replication using Paxos

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

Immediate Consistency

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

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

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

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

Can implement custom security layer via applications

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.