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

System Properties Comparison BaseX vs. GeoMesa vs. Google Cloud Firestore 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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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 MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Native XML DBMS

Spatial DBMS

Document store

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

Score	1.56
Rank	#141	Overall
	#4	Native XML DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Website

basex.org

www.geomesa.org

firebase.google.com/products/firestore

github.com/torodb/server

Technical documentation

docs.basex.org

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

firebase.google.com/docs/firestore

Developer

BaseX GmbH

CCRi and others

Google

8Kdata

Initial release

2007

2014

2017

2016

Current release

11.2, August 2024

5.0.1, July 2024

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache License 2.0

commercial

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

Java

Scala

Java

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

Server-side scripts

Stored procedures

yes

yes, Firebase Rules & Cloud Functions

Triggers

yes

via events

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication

Source-replica 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

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

multiple readers, single writer

yes

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

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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

XML Injection Attacks: What to Know About XPath, XQuery, XXE & More
18 May 2022, Hashed Out by The SSL Store™

9 Skills You Need to Become a Data Engineer
2 November 2022, KDnuggets

provided by Google 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 Launches Cloud NoSQL Database for Mobile, Web Apps
10 October 2017, ADT Magazine

provided by Google News

Share this page