DBMS > Firebird vs. H2 vs. JaguarDB vs. Snowflake vs. Tkrzw

System Properties Comparison Firebird vs. H2 vs. JaguarDB vs. Snowflake vs. Tkrzw

Editorial information provided by DB-Engines

Name

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.

Performant, highly scalable DBMS for AI and IoT applications

Cloud-based data warehousing service for structured and semi-structured data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

Technical documentation

www.firebirdsql.org/en/reference-manuals

www.h2database.com/html/main.html

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Firebird Foundation

Thomas Mueller

DataJaguar, Inc.

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2000

As fork of Borland's InterBase

2005

2015

2014

2020

Current release

5.0.0, January 2024

2.2.220, July 2023

3.3 July 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

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

Open Source

GPL V3.0

commercial

Open Source

Apache Version 2.0

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

C and C++

Java

C++

the server part. Clients available in other languages

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

hosted

Linux
macOS

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

PSQL

Java Stored Procedures and User-Defined Functions

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

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

Multi-source 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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

using specific database classes

User concepts

Access control

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

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.