DBMS > Amazon DynamoDB vs. Amazon Neptune vs. Atos Standard Common Repository vs. Microsoft Azure Table Storage vs. OpenEdge

System Properties Comparison Amazon DynamoDB vs. Amazon Neptune vs. Atos Standard Common Repository vs. Microsoft Azure Table Storage vs. OpenEdge

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 Wide Column Store for rapid development using massive semi-structured datasets

Application development environment with integrated database management system

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Document store
Key-value store

Wide column store

Relational 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	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

aws.amazon.com/dynamodb

aws.amazon.com/neptune

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

azure.microsoft.com/en-us/services/storage/tables

www.progress.com/openedge

Technical documentation

docs.aws.amazon.com/dynamodb

aws.amazon.com/neptune/developer-resources

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Amazon

Atos Convergence Creators

Microsoft

Progress Software Corporation

Initial release

2012

2017

2016

2012

1984

Current release

1703

OpenEdge 12.2, March 2020

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

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

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

yes

close to SQL 92

APIs and other access methods

RESTful HTTP API

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

LDAP

RESTful HTTP API

JDBC
ODBC

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

cell division

Sharding

Implicit feature of the cloud service

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

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)

LDAP bind authentication

Access rights based on private key authentication or shared access signatures

Users and groups

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.