DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. Ingres vs. Newts vs. Trafodion

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. Ingres vs. Newts vs. Trafodion

Editorial information provided by DB-Engines

Name

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

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Well established RDBMS

Time Series DBMS based on Cassandra

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

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	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/dynamodb

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

www.actian.com/databases/ingres

opennms.github.io/newts

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.actian.com/ingres

github.com/OpenNMS/newts/wiki

trafodion.apache.org/documentation.html

Developer

Amazon

Atos Convergence Creators

Actian Corporation

OpenNMS Group

Apache Software Foundation, originally developed by HP

Initial release

2012

2016

1974

originally developed at University Berkely in early 1970s

2014

Current release

1703

11.2, May 2022

2.3.0, February 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

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++, Java

Server operating systems

hosted

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
OS X
Windows

Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

LDAP

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP REST
Java API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

selectable replication factor

based on Cassandra

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via user defined functions and HBase

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

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

LDAP bind authentication

fine grained access rights according to SQL-standard

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.