DBMS > Heroic vs. IRONdb vs. RDF4J vs. SQLite vs. Teradata

System Properties Comparison Heroic vs. IRONdb vs. RDF4J vs. SQLite vs. Teradata

Editorial information provided by DB-Engines

Name

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

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Widely used embeddable, in-process RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Time Series DBMS

RDF store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

github.com/spotify/heroic

www.circonus.com/solutions/time-series-database/

rdf4j.org

www.sqlite.org

www.teradata.com

Technical documentation

spotify.github.io/heroic

docs.circonus.com/irondb/category/getting-started

rdf4j.org/documentation

www.sqlite.org/docs.html

docs.teradata.com

Developer

Spotify

Circonus LLC.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Dwayne Richard Hipp

Teradata

Initial release

2014

2017

2004

2000

1984

Current release

V0.10.20, January 2018

3.46.0 (23 May 2024), May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Public Domain

commercial

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 and C++

Java

Server operating systems

Linux

Linux
OS X
Unix
Windows

server-less

hosted
Linux

Data scheme

schema-free

yes

RDF Schemas

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
PHP
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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes, in Lua

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

fine grained access rights according to SQL-standard

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.