DBMS > Google Cloud Datastore vs. jBASE vs. Percona Server for MongoDB vs. PostGIS

System Properties Comparison Google Cloud Datastore vs. jBASE vs. Percona Server for MongoDB vs. PostGIS

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 robust multi-value DBMS comprising development tools and middleware

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

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

cloud.google.com/datastore

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

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

postgis.net

Technical documentation

cloud.google.com/datastore/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

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

postgis.net/documentation

Developer

Google

Rocket Software (formerly Zumasys)

Percona

Initial release

2008

1991

2015

2005

Current release

5.7

3.4.10-2.10, November 2017

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

GPL v2.0

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

AIX
Linux
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

optional

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

yes

SQL

Support of SQL

SQL-like query language (GQL)

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

proprietary protocol using JSON

Supported programming languages

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

.Net
Basic
Jabbascript
Java

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

Server-side scripts

Stored procedures

using Google App Engine

yes

JavaScript

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Source-replica replication

yes

based on PostgreSQL

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

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

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 can be defined down to the item level

Access rights for users and roles

yes

based on PostgreSQL

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

Recent citations in the news

Google Cloud Platform: Professional Data Engineer certification prep
11 June 2024, oreilly.com

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
4 June 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

provided by Google News

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

MongoDB Performance Tuning
23 May 2024, Database Trends and Applications

Why Isn't the World Upgrading Its Databases?
25 March 2024, The New Stack

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

The essential guide to MongoDB security
2 February 2017, InfoWorld

Open-source developers under corporate pressure to adopt less-permissive licenses, Percona CEO says
13 May 2021, The Register

provided by Google News

Share this page