DBMS > Firebird vs. GeoMesa vs. searchxml vs. VoltDB

System Properties Comparison Firebird vs. GeoMesa vs. searchxml vs. VoltDB

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.

DBMS for structured and unstructured content wrapped with an application server

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Spatial DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.firebirdsql.org

www.geomesa.org

www.searchxml.net/category/products

www.voltdb.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

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

www.searchxml.net/support/handouts

docs.voltdb.com

Developer

Firebird Foundation

CCRi and others

informationpartners gmbh

VoltDB Inc.

Initial release

2000

As fork of Borland's InterBase

2014

2015

2010

Current release

5.0.0, January 2024

5.0.0, May 2024

1.0

11.3, April 2022

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

Apache License 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Windows

Linux
OS X

for development

Data scheme

yes

schema-free

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

only a subset of SQL 99

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP API
WebDAV
XQuery
XSLT

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C++

most other programming languages supported via APIs

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

PSQL

yes

on the application server

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

yes

sychronisation to multiple collections

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

multiple readers, single writer

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

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

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

Users with fine-grained authorization concept

yes

depending on the DBMS used for storage

Domain, group and role-based access control at the document level and for application services

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

DoNot Team's New Firebird Backdoor Hits Pakistan and Afghanistan
23 October 2023, The Hacker News

12 Top Open Source Databases to Consider
1 May 2024, TechTarget

Exploring the Firebird Database
9 August 2023, Open Source For You

Albany Firebirds single-game tickets on sale Friday
29 February 2024, Troy Record

Top Databases for Artificial Intelligence, IoT, Deep Learning, Machine Learning, Data Science, and Other Software Applications
23 July 2023, MarkTechPost

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page