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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

Spatial extension of PostgreSQL

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

arcadedb.com

cloud.google.com/datastore

postgis.net

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

Technical documentation

docs.arcadedb.com

cloud.google.com/datastore/docs

postgis.net/documentation

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

Developer

Arcade Data

Google

Transaction Software GmbH

Initial release

2021

2008

2005

1987

Current release

September 2021

3.4.2, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Java

C and C++

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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, no joins

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

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

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

Server-side scripts

Stored procedures

using Google App Engine

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

Source-replica replication

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

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

relationship in graphs

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.

User concepts

Access control

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

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 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

Share this page