DBMS > Firebird vs. Hive vs. Snowflake vs. Spark SQL vs. Trafodion

System Properties Comparison Firebird vs. Hive vs. Snowflake vs. Spark SQL vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Cloud-based data warehousing service for structured and semi-structured data

Spark SQL is a component on top of 'Spark Core' for structured data processing

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

Technical documentation

www.firebirdsql.org/en/reference-manuals

cwiki.apache.org/confluence/display/Hive/Home

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

trafodion.apache.org/documentation.html

Developer

Firebird Foundation

Apache Software Foundation

initially developed by Facebook

Snowflake Computing Inc.

Apache Software Foundation

Apache Software Foundation, originally developed by HP

Initial release

2000

As fork of Borland's InterBase

2012

2014

Current release

5.0.0, January 2024

3.1.3, April 2022

3.5.0 ( 2.13), September 2023

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

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

Java

Scala

C++, Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

hosted

Linux
OS X
Windows

Linux

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
Thrift

CLI Client
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C++
Java
PHP
Python

JavaScript (Node.js)
Python

Java
Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

PSQL

yes

user defined functions and integration of map-reduce

user defined functions

Java Stored Procedures

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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.

User concepts

Access control

Users with fine-grained authorization concept

Access rights for users, groups and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.