DBMS > Google BigQuery vs. Spark SQL vs. Transbase vs. Ultipa vs. Vitess

System Properties Comparison Google BigQuery vs. Spark SQL vs. Transbase vs. Ultipa vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

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

High performance Graph DBMS supporting HTAP high availability cluster deployment

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	0.19
Rank	#330	Overall
	#30	Graph DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

cloud.google.com/bigquery

spark.apache.org/sql

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

www.ultipa.com

vitess.io

Technical documentation

cloud.google.com/bigquery/docs

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

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

www.ultipa.com/document

vitess.io/docs

Developer

Google

Apache Software Foundation

Transaction Software GmbH

Ultipa

The Linux Foundation, PlanetScale

Initial release

2010

2014

1987

2019

2013

Current release

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free development license

commercial

Open Source

Apache Version 2.0, commercial licenses 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

Scala

C and C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Python
R
Scala

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

C++
Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.