DBMS > EXASOL vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. RDF4J vs. SwayDB

System Properties Comparison EXASOL vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. RDF4J vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

RDF store

Key-value store

Secondary database models

Spatial DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

www.exasol.com

azure.microsoft.com/services/cosmos-db

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

rdf4j.org

swaydb.simer.au

Technical documentation

www.exasol.com/resources

learn.microsoft.com/azure/cosmos-db

rdf4j.org/documentation

Developer

Exasol

Microsoft

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

Simer Plaha

Initial release

2000

2014

2012

2004

2018

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GNU Affero GPL V3.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

Scala

Server operating systems

hosted

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java
Lua
Python
R

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

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

Java
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

Isolation support depends on the API used

Atomic execution of operations

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 for users, groups and roles according to SQL-standard

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.