DBMS > EsgynDB vs. Google Cloud Firestore vs. Infobright vs. Ingres vs. JaguarDB

System Properties Comparison EsgynDB vs. Google Cloud Firestore vs. Infobright vs. Ingres vs. JaguarDB

Editorial information provided by DB-Engines

Name

Description

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Well established RDBMS

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Relational DBMS

Document store

Relational DBMS

Key-value store
Vector DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

www.esgyn.cn

firebase.google.com/products/firestore

ignitetech.com/softwarelibrary/infobrightdb

www.actian.com/databases/ingres

www.jaguardb.com

Technical documentation

firebase.google.com/docs/firestore

docs.actian.com/ingres

www.jaguardb.com/support.html

Developer

Esgyn

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Actian Corporation

DataJaguar, Inc.

Initial release

2015

2017

2005

1974

originally developed at University Berkely in early 1970s

2015

Current release

11.2, May 2022

3.3 July 2023

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

GPL V3.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

C++

the server part. Clients available in other languages

Server operating systems

Linux

hosted

Linux
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

ADO.NET
JDBC
ODBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication

Source-replica replication

Ingres Replicator

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

rights management via user accounts

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

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google's Cloud Firestore is now generally available
31 January 2019, ZDNet

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

provided by Google News

Share this page