DBMS > Google Cloud Firestore vs. JaguarDB vs. Microsoft Azure Table Storage vs. Snowflake vs. Trafodion

System Properties Comparison Google Cloud Firestore vs. JaguarDB vs. Microsoft Azure Table Storage vs. Snowflake vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

Key-value store
Vector DBMS

Wide column store

Relational DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/firestore

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

trafodion.apache.org

Technical documentation

firebase.google.com/docs/firestore

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Google

DataJaguar, Inc.

Microsoft

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2017

2015

2012

2014

Current release

3.3 July 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Open Source

Apache 2.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++

the server part. Clients available in other languages

C++, Java

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

schema-free

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

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

JDBC
ODBC

RESTful HTTP API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Java Stored Procedures

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

rights management via user accounts

Access rights based on private key authentication or shared access signatures

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

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.