DBMS > Amazon DynamoDB vs. Axibase vs. Google Cloud Datastore vs. MonetDB

System Properties Comparison Amazon DynamoDB vs. Axibase vs. Google Cloud Datastore vs. MonetDB

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

A relational database management system that stores data in columns

Primary database model

Document store
Key-value store

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial 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.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Website

aws.amazon.com/dynamodb

axibase.com/docs/atsd/finance

cloud.google.com/datastore

www.monetdb.org

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

www.monetdb.org/Documentation

Developer

Amazon

Axibase Corporation

Google

MonetDB BV

Initial release

2012

2013

2008

2004

Current release

15585

Dec2023 (11.49), December 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

Mozilla Public License 2.0

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

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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

SQL-like query language (GQL)

yes

SQL 2003 with some extensions

APIs and other access methods

RESTful HTTP API

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Go
Java
PHP
Python
R
Ruby

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

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

Server-side scripts

Stored procedures

yes

using Google App Engine

yes, in SQL, C, R

Triggers

yes

by integration with AWS Lambda

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication using Paxos

none

Source-replica replication available in experimental status

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

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

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)

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.