DBMS > Google BigQuery vs. PostGIS vs. Snowflake vs. Transbase

System Properties Comparison Google BigQuery vs. PostGIS vs. Snowflake vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Spatial extension of PostgreSQL

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

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

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

cloud.google.com/bigquery

postgis.net

www.snowflake.com

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

Technical documentation

cloud.google.com/bigquery/docs

postgis.net/documentation

docs.snowflake.net/manuals/index.html

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

Developer

Google

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2010

2005

2014

1987

Current release

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

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

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

Google Cloud Identity & Access Management (IAM)

yes

based on PostgreSQL

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.