DBMS > Amazon DynamoDB vs. Google Cloud Datastore vs. Manticore Search vs. RRDtool

System Properties Comparison Amazon DynamoDB vs. Google Cloud Datastore vs. Manticore Search vs. RRDtool

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

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

Multi-storage database for search, including full-text search.

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

Document store

Search engine

Time Series DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	1.70
Rank	#136	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/dynamodb

cloud.google.com/datastore

manticoresearch.com

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

manual.manticoresearch.com

oss.oetiker.ch/rrdtool/doc

Developer

Amazon

Google

Manticore Software

Tobias Oetiker

Initial release

2012

2008

2017

1999

Current release

6.0, February 2023

1.8.0, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

GPL version 2

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

C++

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

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

HP-UX
Linux

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

yes, details here

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Exporting into and restoring from XML files possible

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

using Google App Engine

user defined functions

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Synchronous replication based on Galera library

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.

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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.