DBMS > Ehcache vs. EsgynDB vs. Firebird vs. Google BigQuery vs. OrigoDB

System Properties Comparison Ehcache vs. EsgynDB vs. Firebird vs. Google BigQuery vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

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

Large scale data warehouse service with append-only tables

A fully ACID in-memory object graph database

Primary database model

Key-value store

Relational DBMS

Document store
Object oriented DBMS

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

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.ehcache.org

www.esgyn.cn

www.firebirdsql.org

cloud.google.com/bigquery

origodb.com

Technical documentation

www.ehcache.org/documentation

www.firebirdsql.org/en/reference-manuals

cloud.google.com/bigquery/docs

origodb.com/docs

Developer

Terracotta Inc, owned by Software AG

Esgyn

Firebird Foundation

Google

Robert Friberg et al

Initial release

2009

2015

2000

As fork of Borland's InterBase

2010

2009

under the name LiveDB

Current release

3.10.0, March 2022

5.0.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Initial Developer's Public License

commercial

Open Source

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.

Implementation language

Java

C++, Java

C and C++

Server operating systems

All OS with a Java VM

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

ADO.NET
JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

Supported programming languages

Java

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net

Server-side scripts

Stored procedures

Java Stored Procedures

PSQL

user defined functions

in JavaScript

yes

Triggers

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication between multi datacenters

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Since BigQuery is designed for querying 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

using a tiered cache-storage approach

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role based authorization

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.