DBMS > Google Cloud Datastore vs. jBASE vs. PostGIS vs. Transbase

System Properties Comparison Google Cloud Datastore vs. jBASE vs. PostGIS vs. Transbase

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

Spatial extension of PostgreSQL

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

cloud.google.com/datastore

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

postgis.net

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/datastore/docs

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

postgis.net/documentation

www.transaction.de/en/products/transbase/features.html

Developer

Google

Rocket Software (formerly Zumasys)

Transaction Software GmbH

Initial release

2008

1991

2005

1987

Current release

5.7

3.4.2, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

free development license

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

Server operating systems

hosted

AIX
Linux
Windows

FreeBSD
Linux
macOS
Solaris
Windows

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Basic
Jabbascript
Java

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

user defined functions

yes

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

based on PostgreSQL

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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.

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

yes

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

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

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

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 is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, netapp.com

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

provided by Google News

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

Share this page