DBMS > Amazon CloudSearch vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Google Cloud Datastore

System Properties Comparison Amazon CloudSearch vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Google Cloud Datastore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Primary database model

Search engine

Document store
Key-value store

Document store

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

aws.amazon.com/cloudsearch

aws.amazon.com/dynamodb

atos.net/en/convergence-creators/portfolio/standard-common-repository

cloud.google.com/datastore

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

Developer

Amazon

Atos Convergence Creators

Google

Initial release

2012

2016

2008

Current release

1703

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

Java

Server operating systems

hosted

Linux

hosted

Data scheme

yes

schema-free

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

yes, details here

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

all search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (GQL)

APIs and other access methods

HTTP API

RESTful HTTP API

LDAP

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

by integration with AWS Lambda

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Multi-source replication using Paxos

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 configuration

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

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

Atomic execution of specific operations

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

authentication via encrypted signatures

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

LDAP bind authentication

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.