DBMS > Apache Jena - TDB vs. Dolt vs. IBM Cloudant vs. Manticore Search vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Jena - TDB vs. Dolt vs. IBM Cloudant vs. Manticore Search vs. Microsoft Azure Cosmos DB

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Database as a Service offering based on Apache CouchDB

Multi-storage database for search, including full-text search.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

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

Score	3.62
Rank	#83	Overall
	#3	RDF stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

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

Website

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

github.com/dolthub/dolt
www.dolthub.com

www.ibm.com/products/cloudant

manticoresearch.com

azure.microsoft.com/services/cosmos-db

Technical documentation

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

docs.dolthub.com

cloud.ibm.com/docs/Cloudant

manual.manticoresearch.com

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

originally developed by HP Labs

DoltHub Inc

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Manticore Software

Microsoft

Initial release

2000

2018

2010

2017

2014

Current release

4.9.0, July 2023

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2

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

Erlang

C++

Server operating systems

All OS with a Java VM

Linux
macOS
Windows

hosted

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

RDF Schemas

yes

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

JSON types

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

CLI Client
HTTP REST

RESTful HTTP/JSON API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

Supported programming languages

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

yes

currently in alpha release

View functions (Map-Reduce) in JavaScript

user defined functions

JavaScript

Triggers

yes

via event handler

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

ACID

atomic operations within a document possible

yes

isolated transactions for atomic changes and binary logging for safe writes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

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

Only one user is configurable, and must be specified in the config file at startup

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.