DBMS > GeoSpock vs. Google Cloud Firestore vs. Memcached vs. Snowflake vs. VoltDB

System Properties Comparison GeoSpock vs. Google Cloud Firestore vs. Memcached vs. Snowflake vs. VoltDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

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 key-value store, originally intended for caching

Cloud-based data warehousing service for structured and semi-structured data

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

Secondary database models

Time Series DBMS

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

geospock.com

firebase.google.com/products/firestore

www.memcached.org

www.snowflake.com

www.voltdb.com

Technical documentation

firebase.google.com/docs/firestore

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

GeoSpock

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2017

2003

2014

2010

Current release

2.0, September 2019

1.6.27, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

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

Java, Javascript

Java, C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux
OS X

for development

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

only a subset of SQL 99

APIs and other access methods

JDBC

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

Proprietary protocol

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Java

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

Access rights for users can be defined per table

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept, user roles and pluggable authentication

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.