DBMS > Amazon DynamoDB vs. Amazon Neptune vs. Atos Standard Common Repository vs. Ehcache

System Properties Comparison Amazon DynamoDB vs. Amazon Neptune vs. Atos Standard Common Repository vs. Ehcache

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

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

Fast, reliable graph database built for the cloud

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

A widely adopted Java cache with tiered storage options

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Document store
Key-value store

Key-value store

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

Score	69.14
Rank	#17	Overall
	#2	Document stores
	#2	Key-value stores

Score	2.31
Rank	#115	Overall
	#6	Graph DBMS
	#3	RDF stores

Score	7.27
Rank	#55	Overall
	#7	Key-value stores

Website

aws.amazon.com/dynamodb

aws.amazon.com/neptune

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

www.ehcache.org

Technical documentation

docs.aws.amazon.com/dynamodb

aws.amazon.com/neptune/developer-resources

www.ehcache.org/documentation

Developer

Amazon

Atos Convergence Creators

Terracotta Inc, owned by Software AG

Initial release

2012

2017

2016

2009

Current release

1703

3.8.1, September 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache Version 2; commercial licenses available

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

All OS with a Java VM

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin 3.3

LDAP

JCache

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages with LDAP bindings

Java

Server-side scripts

Stored procedures

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

cell division

Sharding

by using Terracotta Server

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas

yes

by using Terracotta Server

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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 configuration

Tunable Consistency (Strong, Eventual, Weak)

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Atomic execution of specific operations

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

using a tiered cache-storage approach

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)

LDAP bind authentication

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.