DBMS > Apache Jena - TDB vs. Sadas Engine vs. ScyllaDB vs. SiriDB vs. SQLite

System Properties Comparison Apache Jena - TDB vs. Sadas Engine vs. ScyllaDB vs. SiriDB 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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Cassandra and DynamoDB compatible wide column store

Open Source Time Series DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Key-value store

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

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series 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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.scylladb.com

docs.siridb.com

www.sqlite.org/docs.html

Developer

Apache Software Foundation

originally developed by HP Labs

SADAS s.r.l.

ScyllaDB

Cesbit

Dwayne Richard Hipp

Initial release

2000

2006

2015

2017

2000

Current release

4.9.0, July 2023

8.0

ScyllaDB Open Source 5.4.1, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

free trial version available

Open Source

Open Source (AGPL), commercial license available

Open Source

MIT License

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

AIX
Linux
Windows

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

Numeric data

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.

Secondary indexes

yes

cluster global secondary indices

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements (CQL)

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

JDBC
ODBC
Proprietary protocol

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

.Net
C
C#
C++
Groovy
Java
PHP
Python

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

yes, Lua

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Representation of geographical distribution of servers is possible

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

Atomicity and isolation are supported for single operations

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

managed by 'Learn by Usage'

yes

in-memory tables

yes

User concepts

Access control

Access control via Jena Security

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per object

simple rights management via user accounts

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.