DBMS > Google BigQuery vs. Google Cloud Spanner vs. Graph Engine vs. Spark SQL vs. STSdb

System Properties Comparison Google BigQuery vs. Google Cloud Spanner vs. Graph Engine vs. Spark SQL vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Key-value store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

cloud.google.com/bigquery

cloud.google.com/spanner

www.graphengine.io

spark.apache.org/sql

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/spanner/docs

www.graphengine.io/docs/manual

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

Developer

Google

Microsoft

Apache Software Foundation

STS Soft SC

Initial release

2010

2017

2010

2014

2011

Current release

3.5.0 ( 2.13), September 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

GPLv2, commercial license 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

.NET and C

Scala

Server operating systems

hosted

.NET

Linux
OS X
Windows

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

Query statements complying to ANSI 2011

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC

.NET Client API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

C#
C++
F#
Visual Basic

Java
Python
R
Scala

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication with 3 replicas for regional instances.

none

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

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Strict serializable isolation

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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)

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

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.