DBMS > Apache Jena - TDB vs. Datomic vs. FatDB vs. GeoMesa vs. Yaacomo

System Properties Comparison Apache Jena - TDB vs. Datomic vs. FatDB vs. GeoMesa vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

RDF store

Relational DBMS

Document store
Key-value store

Spatial DBMS

Relational DBMS

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

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Website

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

www.datomic.com

www.geomesa.org

yaacomo.com

Technical documentation

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

docs.datomic.com

www.geomesa.org/documentation/stable/user/index.html

Developer

Apache Software Foundation

originally developed by HP Labs

Cognitect

FatCloud

CCRi and others

Q2WEB GmbH

Initial release

2000

2012

2014

2009

Current release

4.9.0, July 2023

1.0.6735, June 2023

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

limited edition free

commercial

Open Source

Apache License 2.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, Clojure

Scala

Server operating systems

All OS with a Java VM

Windows

Android
Linux
Windows

Data scheme

yes

RDF Schemas

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC

Supported programming languages

Java

Clojure
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

via applications

Triggers

yes

via event handler

By using transaction functions

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

depending on storage layer

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

depending on storage layer

yes

User concepts

Access control

Access control via Jena Security

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Sparql Secrets In Jena-Fuseki - DataScienceCentral.com
24 July 2022, Data Science Central

Extract and query knowledge graphs using Apache Jena (SPARQL Engine)
4 December 2019, Towards Data Science

A catalogue with semantic annotations makes multilabel datasets FAIR | Scientific Reports
4 May 2022, Nature.com

MarkLogic Hones Its Triple Store
18 August 2015, Datanami

How relevant is data analytics to businesses today?
21 August 2016, The Sociable

provided by Google News

Stanchion Turns SQLite Into A Column Store
15 February 2024, iProgrammer

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

provided by Google News

Share this page