DBMS > Firebird vs. GeoMesa vs. SQLite vs. Stardog

System Properties Comparison Firebird vs. GeoMesa vs. SQLite vs. Stardog

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used embeddable, in-process RDBMS

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

Technical documentation

www.firebirdsql.org/en/reference-manuals

www.geomesa.org/documentation/stable/user/index.html

www.sqlite.org/docs.html

docs.stardog.com

Developer

Firebird Foundation

CCRi and others

Dwayne Richard Hipp

Stardog-Union

Initial release

2000

As fork of Borland's InterBase

2014

2000

2010

Current release

5.0.0, January 2024

4.0.5, February 2024

3.45.3 (15 April 2024), April 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache License 2.0

Open Source

Public Domain

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Scala

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

server-less

Linux
macOS
Windows

Data scheme

yes

dynamic column types

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

SQL-92 is not fully supported

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

PSQL

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

via file-system locks

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.

depending on storage layer

yes

User concepts

Access control

Users with fine-grained authorization concept

yes

depending on the DBMS used for storage

Access rights for users and 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.