DBMS > Apache Jena - TDB vs. Prometheus vs. RavenDB vs. Snowflake vs. TigerGraph

System Properties Comparison Apache Jena - TDB vs. Prometheus vs. RavenDB vs. Snowflake vs. TigerGraph

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

Open-source Time Series DBMS and monitoring system

Open Source Operational and Transactional Enterprise NoSQL Document Database

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

Technical documentation

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

prometheus.io/docs

ravendb.net/docs

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Apache Software Foundation

originally developed by HP Labs

Hibernating Rhinos

Snowflake Computing Inc.

Initial release

2000

2015

2010

2014

2017

Current release

4.9.0, July 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

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

C++

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Linux

Data scheme

yes

RDF Schemas

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

SQL-like query language (GSQL)

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

via event handler

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by Federation

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

TDB Transactions

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

Access control via Jena Security

Authorization levels configured per client per database

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.