DBMS > Apache Jena - TDB vs. BigchainDB vs. Linter vs. Snowflake vs. SQLite

System Properties Comparison Apache Jena - TDB vs. BigchainDB vs. Linter vs. Snowflake 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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

RDBMS for high security requirements

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

Widely used embeddable, in-process RDBMS

Primary database model

RDF store

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

Technical documentation

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

bigchaindb.readthedocs.io/en/latest

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation

originally developed by HP Labs

relex.ru

Snowflake Computing Inc.

Dwayne Richard Hipp

Initial release

2000

2016

1990

2014

2000

Current release

4.9.0, July 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

Open Source

AGPL v3

commercial

Open Source

Public Domain

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

Python

C and C++

Server operating systems

All OS with a Java VM

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

server-less

Data scheme

yes

RDF Schemas

schema-free

yes

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

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

CLI Client
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript (Node.js)
Python

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

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

Triggers

yes

via event handler

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes,with MongoDB ord RethinkDB

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

yes

fine grained access rights according to SQL-standard

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

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.