DBMS > Ehcache vs. Firebird vs. IBM Db2 warehouse vs. MySQL

System Properties Comparison Ehcache vs. Firebird vs. IBM Db2 warehouse vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

Cloud-based data warehousing service

Widely used open source RDBMS

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	1.26
Rank	#162	Overall
	#73	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.ehcache.org

www.firebirdsql.org

www.ibm.com/products/db2/warehouse

www.mysql.com

Technical documentation

www.ehcache.org/documentation

www.firebirdsql.org/en/reference-manuals

dev.mysql.com/doc

Developer

Terracotta Inc, owned by Software AG

Firebird Foundation

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2009

2000

As fork of Borland's InterBase

2014

1995

Current release

3.10.0, March 2022

5.0.1, August 2024

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Initial Developer's Public License

commercial

Open Source

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

Server operating systems

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JCache

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

PL/SQL, SQL PL

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

yes

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

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

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

using a tiered cache-storage approach

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

fine grained access rights according to SQL-standard

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.