DBMS > Apache Jena - TDB vs. Google BigQuery vs. TempoIQ vs. TimescaleDB vs. ToroDB

System Properties Comparison Apache Jena - TDB vs. Google BigQuery vs. TempoIQ vs. TimescaleDB vs. ToroDB

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A RDF storage and query DBMS, shipped as an optional-use component of the Apache Jena framework

Large scale data warehouse service with append-only tables

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A MongoDB-compatible JSON document store, built on top of PostgreSQL

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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

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

cloud.google.com/bigquery

tempoiq.com (offline)

www.timescale.com

github.com/torodb/server

Technical documentation

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

cloud.google.com/bigquery/docs

docs.timescale.com

Developer

Apache Software Foundation

originally developed by HP Labs

Google

TempoIQ

Timescale

8Kdata

Initial release

2000

2010

2012

2017

2016

Current release

4.9.0, July 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

Apache 2.0

Open Source

AGPL-V3

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

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Windows

All OS with a Java 7 VM

Data scheme

yes

RDF Schemas

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

yes

string, integer, double, boolean, date, object_id

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

full PostgreSQL SQL syntax

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript

Node.js
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

via event handler

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with hot standby and reads on replicas

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

Since BigQuery is designed for querying data

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

simple authentication-based access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.