DBMS > EsgynDB vs. Firebase Realtime Database vs. H2GIS vs. Microsoft Azure Cosmos DB

System Properties Comparison EsgynDB vs. Firebase Realtime Database vs. H2GIS vs. Microsoft Azure Cosmos DB

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

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

Spatial extension of H2

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.esgyn.cn

firebase.google.com/products/realtime-database

www.h2gis.org

azure.microsoft.com/services/cosmos-db

Technical documentation

firebase.google.com/docs/database

www.h2gis.org/docs/home

learn.microsoft.com/azure/cosmos-db

Developer

Esgyn

Google

acquired by Google 2014

CNRS

Microsoft

Initial release

2015

2012

2013

2014

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

commercial

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

Linux

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

Java Stored Procedures

limited functionality with using 'rules'

yes

based on H2

JavaScript

Triggers

Callbacks are triggered when data changes

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

based on H2

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

yes

based on H2

Access rights can be defined down to the item level

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.