DBMS > GeoMesa vs. Google Cloud Firestore vs. GridDB vs. ToroDB

System Properties Comparison GeoMesa vs. Google Cloud Firestore vs. GridDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

Scalable in-memory time series database optimized for IoT and Big Data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Website

www.geomesa.org

firebase.google.com/products/firestore

griddb.net

github.com/torodb/server

Technical documentation

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

firebase.google.com/docs/firestore

docs.griddb.net

Developer

CCRi and others

Google

Toshiba Corporation

8Kdata

Initial release

2014

2017

2013

2016

Current release

5.0.1, July 2024

5.1, August 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

AGPL-V3

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

C++

Java

Server operating systems

hosted

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

string, integer, double, boolean, date, object_id

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

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Supported programming languages

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

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

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID at container level

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

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.

Access rights for users can be defined per database

Access rights for users and roles

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 Choose
8 March 2024, Appinventiv

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

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

NoSQL on the Cloud With Python
7 August 2020, Towards Data Science

Google’s NoSQL database service Cloud Firestore now up for grabs
1 February 2019, Daily Host News

provided by Google News

TOSHIBA DIGITAL SOLUTIONS CORPORATION
1 November 2020, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data Management
3 December 2019, global.toshiba

Amazon Proposes to Develop New Data Center Campus in Virginia
26 August 2022, w.media

’s SQL Interface, Aims to Accelerate Open Innovation
17 June 2020, global.toshiba

provided by Google News

Share this page