DBMS > Apache Jena - TDB vs. EsgynDB vs. GeoMesa vs. KeyDB

System Properties Comparison Apache Jena - TDB vs. EsgynDB vs. GeoMesa vs. KeyDB

Please select another system to include it in the comparison.

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

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

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

Score	3.85
Rank	#86	Overall
	#3	RDF stores

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.80
Rank	#219	Overall
	#31	Key-value stores

Website

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

www.esgyn.cn

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

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

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

docs.keydb.dev

Developer

Apache Software Foundation

originally developed by HP Labs

Esgyn

CCRi and others

EQ Alpha Technology Ltd.

Initial release

2000

2015

2014

2019

Current release

4.9.0, July 2023

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

Apache License 2.0

Open Source

BSD-3

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

Scala

C++

Server operating systems

All OS with a Java VM

Linux

Data scheme

yes

RDF Schemas

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

Java

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Lua

Triggers

yes

via event handler

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

depending on storage layer

Multi-source replication
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

depending on storage layer

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Access control via Jena Security

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

simple password-based access control and ACL

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

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

Are there any Ontology Deployment Framework that can process OWL semantics and allow reasoning?
17 April 2018, ResearchGate

MarkLogic Hones Its Triple Store
18 August 2015, Datanami

Comparing Grakn to Semantic Web Technologies — Part 1/3 | by Tomas Sabat
26 June 2020, Towards Data Science

provided by Google News

Snap snaps up database developer KeyDB to make its infrastructure more snappy
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page