DBMS > BaseX vs. Google Cloud Datastore vs. Snowflake vs. Spark SQL vs. Transbase

System Properties Comparison BaseX vs. Google Cloud Datastore vs. Snowflake vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

Primary database model

Native XML DBMS

Document store

Relational DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

basex.org

cloud.google.com/datastore

www.snowflake.com

spark.apache.org/sql

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

Technical documentation

docs.basex.org

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

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

Developer

BaseX GmbH

Google

Snowflake Computing Inc.

Apache Software Foundation

Transaction Software GmbH

Initial release

2007

2008

2014

1987

Current release

11.0, June 2024

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

Apache 2.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

Scala

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

XQuery supports types

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 (GQL)

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

CLI Client
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

JavaScript (Node.js)
Python

Java
Python
R
Scala

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

Server-side scripts

Stored procedures

yes

using Google App Engine

user defined functions

yes

Triggers

yes

via events

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

none

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

multiple readers, single writer

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

Users with fine-grained authorization concept on 4 levels

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

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

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.