DBMS > GeoSpock vs. Google Cloud Firestore vs. Realm vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison GeoSpock vs. Google Cloud Firestore vs. Realm vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

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

SAP Advantage Database Server seems to be discontinued. Therefore it is 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.

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geospock.com

firebase.google.com/products/firestore

realm.io

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

firebase.google.com/docs/firestore

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

Google

Realm, acquired by MongoDB in May 2019

Sybase, SAP

Snowflake Computing Inc.

Initial release

2017

2014

1993

2014

Current release

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

commercial

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

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

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

APIs and other access methods

JDBC

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

runs within the applications so server-side scripts are unnecessary

yes

user defined functions

Triggers

yes, with Cloud Functions

yes

Change Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

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 capabilities

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

yes

In-Memory realm

caching of (temporary) tables can be configured

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

fine grained access rights according to SQL-standard

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

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.