DBMS > Apache Drill vs. Apache Jena - TDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison Apache Drill vs. Apache Jena - TDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Document store
Relational DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	3.85
Rank	#86	Overall
	#3	RDF stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

drill.apache.org

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

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

drill.apache.org/docs

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

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

originally developed by HP Labs

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

Initial release

2012

2000

2013

1992

2003

Current release

1.20.3, January 2023

4.9.0, July 2023

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache License, Version 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

RDF Schemas

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

C++

Java

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

Database mirroring

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

yes

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Access control via Jena Security

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.