DBMS > Firebird vs. Google BigQuery vs. OpenEdge vs. Riak KV

System Properties Comparison Firebird vs. Google BigQuery vs. OpenEdge vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

Application development environment with integrated database management system

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.firebirdsql.org

cloud.google.com/bigquery

www.progress.com/openedge

Technical documentation

www.firebirdsql.org/en/reference-manuals

cloud.google.com/bigquery/docs

documentation.progress.com/output/ua/OpenEdge_latest

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Firebird Foundation

Google

Progress Software Corporation

OpenSource, formerly Basho Technologies

Initial release

2000

As fork of Borland's InterBase

2010

1984

2009

Current release

5.0.0, January 2024

OpenEdge 12.2, March 2020

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

Open Source

Apache version 2, commercial enterprise edition

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++

Erlang

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Data scheme

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

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

close to SQL 92

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

PSQL

user defined functions

in JavaScript

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

since Version 11.4

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

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.

User concepts

Access control

Users with fine-grained authorization concept

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users and groups

yes, using Riak Security

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.