DBMS > Amazon Redshift vs. Firebird vs. InfinityDB vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Firebird vs. InfinityDB vs. TerminusDB

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

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

A Java embedded Key-Value Store which extends the Java Map interface

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	0.00
Rank	#383	Overall
	#59	Key-value stores

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

www.firebirdsql.org

boilerbay.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.firebirdsql.org/en/reference-manuals

boilerbay.com/infinitydb/manual

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Firebird Foundation

Boiler Bay Inc.

DataChemist Ltd.

Initial release

2012

2000

As fork of Borland's InterBase

2002

2018

Current release

5.0.1, August 2024

4.0

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

Open Source

GPL 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

C and C++

Java

Prolog, Rust

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

Linux

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

PSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

in-memory journaling

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

Users with fine-grained authorization concept

Role-based access control

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.