DBMS > Firebird vs. GeoSpock vs. MySQL vs. SpatiaLite

System Properties Comparison Firebird vs. GeoSpock vs. MySQL vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

Spatial extension of SQLite

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.firebirdsql.org

geospock.com

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

www.firebirdsql.org/en/reference-manuals

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Firebird Foundation

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Initial release

2000

As fork of Borland's InterBase

1995

2008

Current release

5.0.0, January 2024

2.0, September 2019

8.4.0, April 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java, Javascript

C and C++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Data scheme

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

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

PSQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

yes

table locks or row locks depending on storage engine

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

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

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.