DBMS > Firebird vs. JanusGraph vs. MySQL vs. TerminusDB

System Properties Comparison Firebird vs. JanusGraph vs. MySQL vs. TerminusDB

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.janusgraph.org

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Firebird Foundation

Linux Foundation; originally developed as Titan by Aurelius

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2000

As fork of Borland's InterBase

2017

1995

2018

Current release

5.0.0, January 2024

0.6.3, February 2023

8.4.0, April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java

C and C++

Prolog, Rust

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Clojure
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

PSQL

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Users with fine-grained authorization concept

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

no user groups or roles

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.