DBMS > EsgynDB vs. Firebird vs. GeoMesa vs. Riak KV

System Properties Comparison EsgynDB vs. Firebird vs. GeoMesa vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.esgyn.cn

www.firebirdsql.org

www.geomesa.org

Technical documentation

www.firebirdsql.org/en/reference-manuals

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Esgyn

Firebird Foundation

CCRi and others

OpenSource, formerly Basho Technologies

Initial release

2015

2000

As fork of Borland's InterBase

2014

2009

Current release

5.0.0, January 2024

4.0.5, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

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

C and C++

Scala

Erlang

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
OS X

Data scheme

yes

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

PSQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

depending on storage layer

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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.

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

yes

depending on the DBMS used for storage

yes, using Riak Security

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

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

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

FIREBIRD'S HUBBARD TALKS DATA, AI, TIKTOK
14 December 2023, HITS Daily Double

US and Australian police arrested Firebird RAT author and operator
15 April 2024, Security Affairs

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

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page