DBMS > Amazon Redshift vs. Databricks vs. Google BigQuery vs. Microsoft Azure Synapse Analytics

System Properties Comparison Amazon Redshift vs. Databricks vs. Google BigQuery vs. Microsoft Azure Synapse Analytics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Large scale data warehouse service with append-only tables

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Website

aws.amazon.com/redshift

www.databricks.com

cloud.google.com/bigquery

azure.microsoft.com/services/synapse-analytics

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

cloud.google.com/bigquery/docs

docs.microsoft.com/azure/synapse-analytics

Developer

Amazon (based on PostgreSQL)

Databricks

Google

Microsoft

Initial release

2012

2013

2010

2016

License

Commercial or Open Source

commercial

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

Server operating systems

hosted

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Python
R
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
PHP

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

user defined functions

in JavaScript

Transact SQL

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

informational only, not enforced by the system

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.