DBMS > GeoMesa vs. Google Cloud Firestore vs. TimesTen vs. VoltDB

System Properties Comparison GeoMesa vs. Google Cloud Firestore vs. TimesTen vs. VoltDB

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.

In-Memory RDBMS compatible to Oracle

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Spatial DBMS

Document store

Relational DBMS

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	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

firebase.google.com/products/firestore

www.oracle.com/database/technologies/related/timesten.html

www.voltdb.com

Technical documentation

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

firebase.google.com/docs/firestore

docs.oracle.com/database/timesten-18.1

docs.voltdb.com

Developer

CCRi and others

Google

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

VoltDB Inc.

Initial release

2014

2017

1998

2010

Current release

5.0.0, May 2024

11 Release 2 (11.2.2.8.0)

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X

for development

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

only a subset of SQL 99

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

C
C++
Java
PL/SQL

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

PL/SQL

Java

Triggers

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

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

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

yes

Snapshots and command 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

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

Users and roles with access to stored procedures

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

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

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page