DBMS > Amazon SimpleDB vs. Atos Standard Common Repository vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Titan

System Properties Comparison Amazon SimpleDB vs. Atos Standard Common Repository vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Titan

Editorial information provided by DB-Engines

Name

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

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Globally distributed, horizontally scalable, multi-model database service

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Key-value store

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

aws.amazon.com/simpledb

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

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/cosmos-db

github.com/thinkaurelius/titan

Technical documentation

docs.aws.amazon.com/simpledb

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

github.com/thinkaurelius/titan/wiki

Developer

Amazon

Atos Convergence Creators

Microsoft

Aurelius, owned by DataStax

Initial release

2007

2016

1992

2014

2012

Current release

1703

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache license, version 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

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

JSON types

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

All columns are indexed automatically

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

RESTful HTTP API

LDAP

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

All languages with LDAP bindings

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

yes

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

cell division

none

Sharding

Implicit feature of the cloud service

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via Faunus, a graph analytics engine

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Concurrent data updates can be detected by the application

Atomic execution of specific operations

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

a simple user-level security was built in till version Access 2003

Access rights can be defined down to the item level

User authentification and security via Rexster Graph Server

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.