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

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

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

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

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

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	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.esgyn.cn

firebase.google.com/products/realtime-database

www.h2gis.org

www.voltdb.com

yaacomo.com

Technical documentation

firebase.google.com/docs/database

www.h2gis.org/docs/home

docs.voltdb.com

Developer

Esgyn

Google

acquired by Google 2014

CNRS

VoltDB Inc.

Q2WEB GmbH

Initial release

2015

2012

2013

2010

2009

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

Open Source

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

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

Java, C++

Server operating systems

Linux

hosted

Linux
OS X

for development

Android
Linux
Windows

Data scheme

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

only a subset of SQL 99

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

Java

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

Java

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

based on H2

Multi-source replication
Source-replica 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

yes

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

fine grained access rights according to SQL-standard

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

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

Misconfigured Firebase instances leaked 19 million plaintext passwords
19 March 2024, BleepingComputer

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page