DBMS > Amazon DynamoDB vs. Galaxybase vs. Google Cloud Datastore vs. IRONdb

System Properties Comparison Amazon DynamoDB vs. Galaxybase vs. Google Cloud Datastore vs. IRONdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Scalable, ACID-compliant native distributed parallel graph platform

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Primary database model

Document store
Key-value store

Graph DBMS

Document store

Time Series 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.00
Rank	#383	Overall
	#39	Graph DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

aws.amazon.com/dynamodb

galaxybase.com

cloud.google.com/datastore

www.circonus.com/solutions/time-series-database/

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.circonus.com/irondb/category/getting-started

Developer

Amazon

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Google

Circonus LLC.

Initial release

2012

2017

2008

2017

Current release

Nov 20, November 2021

V0.10.20, January 2018

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.

Implementation language

C and Java

C and C++

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

schema-free

Strong typed schema

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

text, numeric, histograms

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)

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

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

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Go
Java
Python

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

user defined procedures and functions

using Google App Engine

yes, in Lua

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

configurable replication factor, datacenter aware

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.

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

Relationships in graphs

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.

yes

User concepts

Access control

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

Role-based access control

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

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.