DBMS > Apache Jena - TDB vs. Atos Standard Common Repository vs. MySQL vs. SpatiaLite

System Properties Comparison Apache Jena - TDB vs. Atos Standard Common Repository vs. MySQL vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Widely used open source RDBMS

Spatial extension of SQLite

Primary database model

RDF store

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	2.91
Rank	#93	Overall
	#3	RDF stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Website

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

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

originally developed by HP Labs

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Initial release

2000

2016

1995

2008

Current release

4.9.0, July 2023

1703

9.0.0, July 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C and C++

C++

Server operating systems

All OS with a Java VM

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

RDF Schemas

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

TDB Transactions

Atomic execution of specific operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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 control via Jena Security

LDAP bind authentication

Users with fine-grained authorization concept

no user groups or 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.