DBMS > FatDB vs. GeoMesa vs. Google Cloud Firestore vs. HugeGraph vs. Yaacomo

System Properties Comparison FatDB vs. GeoMesa vs. Google Cloud Firestore vs. HugeGraph vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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.

A fast-speed and highly-scalable Graph DBMS

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

Primary database model

Document store
Key-value store

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Website

www.geomesa.org

firebase.google.com/products/firestore

github.com/hugegraph
hugegraph.apache.org

yaacomo.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

firebase.google.com/docs/firestore

hugegraph.apache.org/docs

Developer

FatCloud

CCRi and others

Google

Baidu

Q2WEB GmbH

Initial release

2012

2014

2017

2018

2009

Current release

4.0.5, February 2024

0.9

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

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

Scala

Java

Server operating systems

Windows

hosted

Linux
macOS
Unix

Android
Linux
Windows

Data scheme

schema-free

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

also supports composite index and range index

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC

Supported programming languages

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

Groovy
Java
Python

Server-side scripts

Stored procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

asynchronous Gremlin script jobs

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Multi-source replication

yes

depending on used storage backend, e.g. Cassandra and HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

yes

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.

depending on storage layer

yes

User concepts

Access control

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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

Users, roles and permissions

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

Firestore and Python | NoSQL on Google Cloud
7 August 2020, Towards Data Science

provided by Google News

Critical Apache HugeGraph Flaw Let Attackers Execute Remote Code
23 April 2024, GBHackers

provided by Google News

Share this page