DBMS > GeoMesa vs. Google Cloud Firestore vs. Sadas Engine vs. TerminusDB

System Properties Comparison GeoMesa vs. Google Cloud Firestore vs. Sadas Engine vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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	0.00
Rank	#385	Overall
	#159	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

www.geomesa.org

firebase.google.com/products/firestore

www.sadasengine.com

terminusdb.com

Technical documentation

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

firebase.google.com/docs/firestore

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

terminusdb.github.io/terminusdb/#

Developer

CCRi and others

Google

SADAS s.r.l.

DataChemist Ltd.

Initial release

2014

2017

2006

2018

Current release

5.0.1, July 2024

8.0

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free trial version available

Open Source

GPL 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++

Prolog, Rust

Server operating systems

hosted

AIX
Linux
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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

managed by 'Learn by Usage'

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, groups and roles according to SQL-standard

Role-based access control

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

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source Critical Asset Management System (CAMS) to help cities become disaster and climate resilient
12 April 2022, United Nations Office for Disaster Risk Reduction

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

Bus Terminus Update – April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Share this page