DBMS > Amazon Redshift vs. Apache Impala vs. EsgynDB vs. Firebird vs. OrigoDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. EsgynDB vs. Firebird vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

www.firebirdsql.org/en/reference-manuals

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Esgyn

Firebird Foundation

Robert Friberg et al

Initial release

2012

2013

2015

2000

As fork of Borland's InterBase

2009

under the name LiveDB

Current release

4.1.0, June 2022

5.0.0, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

Initial Developer's Public License

Open Source

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

C and C++

Server operating systems

hosted

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Java Stored Procedures

PSQL

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication between multi datacenters

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

depending on model

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

Write ahead log

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Role based authorization

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.