DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. Blazegraph vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. Blazegraph vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

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

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Database as a Service offering with high compatibility to Microsoft SQL Server

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial 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	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

aws.amazon.com/dynamodb

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

blazegraph.com

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/dynamodb

wiki.blazegraph.com

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon

Atos Convergence Creators

Blazegraph

Microsoft

SAP

formerly Sybase

Initial release

2012

2016

2006

2010

1992

Current release

1703

2.1.5, March 2019

V12

17, July 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

extended commercial license available

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

C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
OS X
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

RDF literal 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

SQL

Support of SQL

SPARQL is used as query language

yes

APIs and other access methods

RESTful HTTP API

LDAP

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

yes

Transact SQL

yes, in C/C++, Java, .Net or Perl

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Source-replica replication

Database mirroring

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 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

Atomic execution of specific operations

ACID

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

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

LDAP bind authentication

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.