DBMS > Google Cloud Datastore vs. Percona Server for MongoDB vs. SpaceTime vs. STSdb

System Properties Comparison Google Cloud Datastore vs. Percona Server for MongoDB vs. SpaceTime vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

cloud.google.com/datastore

www.percona.com/mongodb/software/percona-server-for-mongodb

www.mireo.com/spacetime

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/datastore/docs

docs.percona.com/percona-distribution-for-mongodb

Developer

Google

Percona

Mireo

STS Soft SC

Initial release

2008

2015

2020

2011

Current release

3.4.10-2.10, November 2017

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

commercial

Open Source

GPLv2, commercial license available

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

C++

Server operating systems

hosted

Linux

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

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

SQL-like query language (GQL)

A subset of ANSI SQL is implemented

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

proprietary protocol using JSON

RESTful HTTP API

.NET Client API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C#
C++
Python

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Real-time block device replication (DRBD)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

via In-Memory Engine

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles

yes

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

Recent citations in the news

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Google App Engine
26 April 2024, TechTarget

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Percona Delivers Open Source In-Memory Storage Engine for Percona Server for MongoDB
20 August 2016, insideBIGDATA

Is database-as-a-service in Percona’s future?
23 May 2022, VentureBeat

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

How to deploy the Percona database performance monitor with Docker
20 September 2022, TechRepublic

provided by Google News

Share this page