DBMS > Apache Jena - TDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Tigris

System Properties Comparison Apache Jena - TDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Tigris

Editorial information provided by DB-Engines

Name

Description

A RDF storage and query DBMS, shipped as an optional-use component of the Apache Jena framework

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

RDF store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	2.91
Rank	#93	Overall
	#3	RDF stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

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

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	0.05
Rank	#359	Overall
	#50	Document stores
	#52	Key-value stores
	#23	Search engines
	#37	Time Series DBMS

Website

jena.apache.org/documentation/tdb/index.html

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

www.tigrisdata.com

Technical documentation

jena.apache.org/documentation/tdb/index.html

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/data-explorer

www.tigrisdata.com/docs

Developer

Apache Software Foundation

originally developed by HP Labs

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Tigris Data, Inc.

Initial release

2000

2010

2014

2019

2022

Current release

4.9.0, July 2023

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

Apache 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

Erlang

Server operating systems

All OS with a Java VM

hosted

Linux
macOS
Windows

Data scheme

yes

RDF Schemas

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

RESTful HTTP/JSON API

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

JavaScript

Yes, possible languages: KQL, Python, R

Triggers

yes

via event handler

yes

JavaScript

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

TDB Transactions

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access control via Jena Security

Access rights for users can be defined per database

Access rights can be defined down to the item level

Azure Active Directory Authentication

Access rights for users and roles

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.