DBMS > Apache Drill vs. Bangdb vs. Google BigQuery vs. Spark SQL vs. SwayDB

System Properties Comparison Apache Drill vs. Bangdb vs. Google BigQuery vs. Spark SQL vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Converged and high performance database for device data, events, time series, document and graph

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

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series 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

drill.apache.org

bangdb.com

cloud.google.com/bigquery

spark.apache.org/sql

swaydb.simer.au

Technical documentation

drill.apache.org/docs

docs.bangdb.com

cloud.google.com/bigquery/docs

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

Developer

Apache Software Foundation

Sachin Sinha, BangDB

Google

Apache Software Foundation

Simer Plaha

Initial release

2012

2010

2014

2018

Current release

1.20.3, January 2023

BangDB 2.0, October 2021

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

BSD 3

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

C, C++

Scala

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL like support with command line tool

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C++

C
C#
C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Python
R
Scala

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes, Notifications (with Streaming only)

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable consistency, set CAP knob accordingly

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

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes, run db with in-memory only mode

yes

User concepts

Access control

Depending on the underlying data source

yes (enterprise version only)

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

Google Cloud Identity & 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.