DBMS > EsgynDB vs. Firebase Realtime Database vs. H2GIS vs. Snowflake vs. VoltDB

System Properties Comparison EsgynDB vs. Firebase Realtime Database vs. H2GIS vs. Snowflake vs. VoltDB

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

Cloud-based data warehousing service for structured and semi-structured data

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Relational 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	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.esgyn.cn

firebase.google.com/products/realtime-database

www.h2gis.org

www.snowflake.com

www.voltdb.com

Technical documentation

firebase.google.com/docs/database

www.h2gis.org/docs/home

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Esgyn

Google

acquired by Google 2014

CNRS

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2015

2012

2013

2014

2010

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux

hosted

Linux
OS X

for development

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

Java

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

limited functionality with using 'rules'

yes

based on H2

user defined functions

Java

Triggers

Callbacks are triggered when data changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

based on H2

yes

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and roles with access to stored procedures

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.