DBMS > Firebird vs. OpenQM vs. RDF4J vs. SQLite

System Properties Comparison Firebird vs. OpenQM vs. RDF4J vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.firebirdsql.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

rdf4j.org

www.sqlite.org

Technical documentation

www.firebirdsql.org/en/reference-manuals

rdf4j.org/documentation

www.sqlite.org/docs.html

Developer

Firebird Foundation

Rocket Software, originally Martin Phillips

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

Dwayne Richard Hipp

Initial release

2000

As fork of Borland's InterBase

1993

2004

2000

Current release

5.0.0, January 2024

3.4-12

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

GPLv2, extended commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Public Domain

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

C and C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Unix
Windows

server-less

Data scheme

yes

with some exceptions

yes

RDF Schemas

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

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

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

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

Server-side scripts

Stored procedures

PSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

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

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

yes

via file-system locks

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

Users with fine-grained authorization concept

Access rights can be defined down to the item level

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.