DBMS > Firebird vs. PostGIS vs. Snowflake vs. TerarkDB

System Properties Comparison Firebird vs. PostGIS vs. Snowflake vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Relational DBMS

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

www.firebirdsql.org

postgis.net

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

www.firebirdsql.org/en/reference-manuals

postgis.net/documentation

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Firebird Foundation

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2000

As fork of Borland's InterBase

2005

2014

2016

Current release

5.0.0, January 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

GPL v2.0

commercial

restricted open source version 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++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Data scheme

yes

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

PSQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

based on PostgreSQL

yes

none

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

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

Users with fine-grained authorization concept

yes

based on PostgreSQL

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

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.