DBMS > Microsoft Azure Cosmos DB vs. RDF4J vs. SAP SQL Anywhere vs. Trafodion

System Properties Comparison Microsoft Azure Cosmos DB vs. RDF4J vs. SAP SQL Anywhere vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Globally distributed, horizontally scalable, multi-model database service

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

RDF store

Relational DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

rdf4j.org

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

trafodion.apache.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

rdf4j.org/documentation

help.sap.com/docs/SAP_SQL_Anywhere

trafodion.apache.org/documentation.html

Developer

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

SAP

formerly Sybase

Apache Software Foundation, originally developed by HP

Initial release

2014

2004

1992

2014

Current release

17, July 2015

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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
OS X
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

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 properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

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

Java
PHP
Python

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

yes

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

Java Stored Procedures

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Source-replica replication

Database mirroring

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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 can be defined down to the item level

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.