DBMS > Amazon Redshift vs. Apache Jena - TDB vs. Firebird vs. Sphinx

System Properties Comparison Amazon Redshift vs. Apache Jena - TDB vs. Firebird vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Firebird is an open source RDBMS forked from Borland's InterBase

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

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

www.firebirdsql.org

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

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

www.firebirdsql.org/en/reference-manuals

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

originally developed by HP Labs

Firebird Foundation

Sphinx Technologies Inc.

Initial release

2012

2000

As fork of Borland's InterBase

2001

Current release

4.9.0, July 2023

5.0.0, January 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache License, Version 2.0

Open Source

Initial Developer's Public License

Open Source

GPL version 2, commercial licence available

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

C and C++

C++

Server operating systems

hosted

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

RDF Schemas

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.

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

yes

PSQL

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

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

informational only, not enforced by the system

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

Features a multi-generational MVCC architecture, readers do not block writers

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Access control via Jena Security

Users with fine-grained authorization concept

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.