DBMS > Apache Jena - TDB vs. EsgynDB vs. Percona Server for MongoDB vs. PostGIS vs. SQLite

System Properties Comparison Apache Jena - TDB vs. EsgynDB vs. Percona Server for MongoDB vs. PostGIS vs. SQLite

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	3.62
Rank	#83	Overall
	#3	RDF stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.esgyn.cn

www.percona.com/mongodb/software/percona-server-for-mongodb

postgis.net

www.sqlite.org

Technical documentation

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

docs.percona.com/percona-distribution-for-mongodb

postgis.net/documentation

www.sqlite.org/docs.html

Developer

Apache Software Foundation

originally developed by HP Labs

Esgyn

Percona

Dwayne Richard Hipp

Initial release

2000

2015

2005

2000

Current release

4.9.0, July 2023

3.4.10-2.10, November 2017

3.4.2, February 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

GPL Version 2

Open Source

GPL v2.0

Open Source

Public Domain

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++, Java

C++

Server operating systems

All OS with a Java VM

Linux

server-less

Data scheme

yes

RDF Schemas

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

All languages supporting JDBC/ODBC/ADO.Net

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Java Stored Procedures

JavaScript

user defined functions

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

Source-replica replication

yes

based on PostgreSQL

none

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

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

via file-system locks

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

via In-Memory Engine

yes

User concepts

Access control

Access control via Jena Security

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

based on PostgreSQL

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.