DBMS > Databricks vs. Google BigQuery vs. Spark SQL vs. SwayDB

System Properties Comparison Databricks vs. Google BigQuery vs. Spark SQL vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

www.databricks.com

cloud.google.com/bigquery

spark.apache.org/sql

swaydb.simer.au

Technical documentation

docs.databricks.com

cloud.google.com/bigquery/docs

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

Developer

Databricks

Google

Apache Software Foundation

Simer Plaha

Initial release

2013

2010

2014

2018

Current release

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GNU Affero GPL V3.0

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

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

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

yes

schema-free

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

with Databricks SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

Python
R
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Python
R
Scala

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Atomic execution of operations

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

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

Google Cloud Identity & Access Management (IAM)

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.