DBMS > BigObject vs. Ehcache vs. Firebird vs. GeoMesa vs. Heroic

System Properties Comparison BigObject vs. Ehcache vs. Firebird vs. GeoMesa vs. Heroic

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

github.com/spotify/heroic

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

www.firebirdsql.org/en/reference-manuals

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

spotify.github.io/heroic

Developer

BigObject, Inc.

Terracotta Inc, owned by Software AG

Firebird Foundation

CCRi and others

Spotify

Initial release

2015

2009

2000

As fork of Borland's InterBase

2014

Current release

3.10.0, March 2022

5.0.0, January 2024

4.0.5, February 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

Open Source

Initial Developer's Public License

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Java

C and C++

Scala

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Data scheme

yes

schema-free

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

via Elasticsearch

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JCache

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

PSQL

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

Source-replica replication

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

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

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

Users with fine-grained authorization concept

yes

depending on the DBMS used for storage

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

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google 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

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

Firebird - Analyst, Digital Marketing (US)
23 February 2024, Music Business Worldwide

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

provided by Google News

Share this page