DBMS > Amazon Redshift vs. BigchainDB vs. dBASE vs. Firebird vs. Firebolt

System Properties Comparison Amazon Redshift vs. BigchainDB vs. dBASE vs. Firebird vs. Firebolt

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

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

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

www.firebirdsql.org/en/reference-manuals

docs.firebolt.io

Developer

Amazon (based on PostgreSQL)

Asthon Tate

Firebird Foundation

Firebolt Analytics Inc.

Initial release

2012

2016

1979

2000

As fork of Borland's InterBase

2020

Current release

dBASE 2019, 2019

5.0.0, January 2024

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

Open Source

Initial Developer's Public License

commercial

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

Python

C and C++

Server operating systems

hosted

Linux

DOS

dBase Classic
Windows

dBase Pro

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

.Net
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Go
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

PSQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

Source-replica replication

depending on storage layer

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

yes

Access rights for users and roles

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.