DBMS > Firebird vs. Google Cloud Datastore vs. H2 vs. Yanza

System Properties Comparison Firebird vs. Google Cloud Datastore vs. H2 vs. Yanza

Please select another system to include it in the comparison.

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Spatial DBMS

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

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Website

www.firebirdsql.org

cloud.google.com/datastore

www.h2database.com

yanza.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

Developer

Firebird Foundation

Google

Thomas Mueller

Yanza

Initial release

2000

As fork of Borland's InterBase

2008

2005

2015

Current release

5.0.0, January 2024

2.2.220, July 2023

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

Open Source

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

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

All OS with a Java VM

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

HTTP API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

PSQL

using Google App Engine

Java Stored Procedures and User-Defined Functions

Triggers

yes

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

yes

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Albany Firebirds single-game tickets on sale Friday
29 February 2024, Troy Record

DoNot Team's New Firebird Backdoor Hits Pakistan and Afghanistan
23 October 2023, The Hacker News

How to Run Multiple Instances of Firebird Server - opensource for you
31 August 2019, Open Source For You

Top 15 Databases to Use in 2024 and Beyond
4 June 2021, Appinventiv

Former Trinity DB Ross stars as Sharks rout Firebirds
1 December 2021, The Florida Times-Union

provided by Google News

Google Cloud is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, netapp.com

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

provided by Google News

Share this page