DBMS > Firebird vs. Graph Engine vs. InterSystems Caché vs. MySQL

System Properties Comparison Firebird vs. Graph Engine vs. InterSystems Caché vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A multi-model DBMS and application server

Widely used open source RDBMS

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.firebirdsql.org

www.graphengine.io

www.intersystems.com/products/cache

www.mysql.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

www.graphengine.io/docs/manual

docs.intersystems.com

dev.mysql.com/doc

Developer

Firebird Foundation

Microsoft

InterSystems

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2000

As fork of Borland's InterBase

2010

1997

1995

Current release

5.0.1, August 2024

2018.1.4, May 2020

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

C and C++

.NET and C

C and C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

.NET

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

depending on used data model

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

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C#
C++
Java

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

Server-side scripts

Stored procedures

PSQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 for users, groups and roles

Users with fine-grained authorization concept

no user groups or 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.