DBMS > Amazon DynamoDB vs. atoti vs. Google Cloud Datastore vs. LevelDB vs. RRDtool

System Properties Comparison Amazon DynamoDB vs. atoti vs. Google Cloud Datastore vs. LevelDB vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

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

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Document store
Key-value store

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	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/dynamodb

atoti.io

cloud.google.com/datastore

github.com/google/leveldb

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/dynamodb

docs.atoti.io

cloud.google.com/datastore/docs

github.com/google/leveldb/blob/main/doc/index.md

oss.oetiker.ch/rrdtool/doc

Developer

Amazon

ActiveViam

Google

Tobias Oetiker

Initial release

2012

2008

2011

1999

Current release

1.23, February 2021

1.8.0, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free versions available

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

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

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

Illumos
Linux
OS X
Windows

HP-UX
Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

SQL-like query language (GQL)

APIs and other access methods

RESTful HTTP API

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

in-process shared library
Pipes

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

Python

using Google App Engine

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

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.

Immediate Consistency

none

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

yes, multi-version concurrency control (MVCC)

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

with automatic compression on writes

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)

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.