DBMS > Firebird vs. H2 vs. Hazelcast vs. Microsoft SQL Server vs. Yanza

System Properties Comparison Firebird vs. H2 vs. Hazelcast vs. Microsoft SQL Server vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A widely adopted in-memory data grid

Microsofts flagship relational DBMS

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Spatial DBMS

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.firebirdsql.org

www.h2database.com

hazelcast.com

www.microsoft.com/en-us/sql-server

yanza.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

www.h2database.com/html/main.html

hazelcast.org/imdg/docs

learn.microsoft.com/en-US/sql/sql-server

Developer

Firebird Foundation

Thomas Mueller

Hazelcast

Microsoft

Yanza

Initial release

2000

As fork of Borland's InterBase

2005

2008

1989

2015

Current release

5.0.0, January 2024

2.2.220, July 2023

5.3.6, November 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Java

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

Linux
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

any language that supports HTTP calls

Server-side scripts

Stored procedures

PSQL

Java Stored Procedures and User-Defined Functions

yes

Event Listeners, Executor Services

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

Replicated Map

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

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

Role-based access control

fine grained access rights according to SQL-standard

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.