DBMS > Firebird vs. Geode vs. Postgres-XL vs. Yanza

System Properties Comparison Firebird vs. Geode vs. Postgres-XL 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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

www.firebirdsql.org

geode.apache.org

www.postgres-xl.org

yanza.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

geode.apache.org/docs

www.postgres-xl.org/documentation

Developer

Firebird Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Yanza

Initial release

2000

As fork of Borland's InterBase

2002

2014

since 2012, originally named StormDB

2015

Current release

5.0.0, January 2024

1.1, February 2017

10 R1, October 2018

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Mozilla public license

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

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

distributed, parallel query execution

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

PSQL

user defined functions

Triggers

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

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

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 per client and object definable

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

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

FIREBIRD'S HUBBARD TALKS DATA, AI, TIKTOK
14 December 2023, HITS Daily Double

Firebird - Analyst, Digital Marketing (US)
23 February 2024, Music Business Worldwide

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

AFP arrests man over alleged creation and sale of 'Firebird' RAT
15 April 2024, iTnews

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven ...
30 June 2018, InfoQ.com

provided by Google News

Share this page