DBMS > Amazon Redshift vs. Firebird vs. Graph Engine vs. Oracle Berkeley DB

System Properties Comparison Amazon Redshift vs. Firebird vs. Graph Engine vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used in-process key-value store

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/redshift

www.firebirdsql.org

www.graphengine.io

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

docs.aws.amazon.com/redshift

www.firebirdsql.org/en/reference-manuals

www.graphengine.io/docs/manual

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon (based on PostgreSQL)

Firebird Foundation

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2000

As fork of Borland's InterBase

2010

1994

Current release

5.0.0, January 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

MIT License

Open Source

commercial license available

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

.NET and C

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

.NET

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

PSQL

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.