DBMS > DataFS vs. EsgynDB vs. Firebase Realtime Database vs. Google BigQuery vs. H2GIS

System Properties Comparison DataFS vs. EsgynDB vs. Firebase Realtime Database vs. Google BigQuery vs. H2GIS

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Large scale data warehouse service with append-only tables

Spatial extension of H2

Primary database model

Secondary database models

Graph DBMS

Relational DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

newdatabase.com

www.esgyn.cn

firebase.google.com/products/realtime-database

cloud.google.com/bigquery

www.h2gis.org

Technical documentation

dev.mobiland.com/Overview.xsp

firebase.google.com/docs/database

cloud.google.com/bigquery/docs

www.h2gis.org/docs/home

Developer

Mobiland AG

Esgyn

Google

acquired by Google 2014

Google

CNRS

Initial release

2018

2015

2012

2010

2013

Current release

1.1.263, October 2022

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

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

C++, Java

Java

Server operating systems

Windows

Linux

hosted

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C#
C++
VB.Net

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

Server-side scripts

Stored procedures

Java Stored Procedures

limited functionality with using 'rules'

user defined functions

in JavaScript

yes

based on H2

Triggers

no, except callback-events from server when changes happened

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

based on H2

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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.

yes

User concepts

Access control

Windows-Profile

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

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

Google Cloud Identity & Access Management (IAM)

yes

based on H2

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.