DBMS > Amazon Redshift vs. Apache Impala vs. Firebird vs. GigaSpaces

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Firebird vs. GigaSpaces

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

Analytic DBMS for Hadoop

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Secondary database models

Document store

Graph DBMS
Search engine

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	0.91
Rank	#197	Overall
	#33	Document stores
	#7	Object oriented DBMS

Website

aws.amazon.com/redshift

impala.apache.org

www.firebirdsql.org

www.gigaspaces.com

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

www.firebirdsql.org/en/reference-manuals

docs.gigaspaces.com/latest/landing.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Firebird Foundation

Gigaspaces Technologies

Initial release

2012

2013

2000

As fork of Borland's InterBase

2000

Current release

4.1.0, June 2022

5.0.1, August 2024

15.5, September 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Initial Developer's Public License

Open Source

Apache Version 2; Commercial licenses 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++

C and C++

Java, C++, .Net

Server operating systems

hosted

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
macOS
Solaris
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.

XML can be used for describing objects metadata

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

SQL-99 for query and DML statements

APIs and other access methods

JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
C++
Java
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

PSQL

yes

Triggers

yes

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept

Role-based access control

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.