DBMS > GeoMesa vs. Google Cloud Firestore vs. H2 vs. LokiJS vs. Tarantool

System Properties Comparison GeoMesa vs. Google Cloud Firestore vs. H2 vs. LokiJS vs. Tarantool

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.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

In-memory JavaScript DBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.geomesa.org

firebase.google.com/products/firestore

www.h2database.com

github.com/techfort/LokiJS

www.tarantool.io

Technical documentation

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

firebase.google.com/docs/firestore

www.h2database.com/html/main.html

techfort.github.io/LokiJS

www.tarantool.io/en/doc

Developer

CCRi and others

Google

Thomas Mueller

Initial release

2014

2017

2005

2014

2008

Current release

5.0.0, May 2024

2.2.220, July 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

JavaScript

C and C++

Server operating systems

hosted

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

BSD
Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

via views

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

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

JDBC
ODBC

JavaScript API

Open binary protocol

Supported programming languages

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

Java

JavaScript

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Java Stored Procedures and User-Defined Functions

View functions in JavaScript

Lua, C and SQL stored procedures

Triggers

yes, with Cloud Functions

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

With clustering: 2 database servers on different computers operate on identical copies of a database

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

none

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

atomic operations within a single collection possible

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes, write ahead logging

In-memory capabilities

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

depending on storage layer

yes

yes, full featured in-memory storage engine with persistence

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.

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

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

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

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

provided by Google News

LokiJS - A JavaScript Database
18 November 2014, iProgrammer

provided by Google News

Tarantool Announces New Enterprise Version With Enhanced Scaling and Monitoring Capabilities
18 May 2018, Newswire

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

VShard — horizontal scaling in Tarantool
7 March 2019, Хабр

Accelerating PHP connectors for Tarantool using Async, Swoole, and Parallel
18 December 2019, Хабр

provided by Google News

Share this page