DBMS > Databricks vs. Google BigQuery vs. Oracle NoSQL vs. TigerGraph

System Properties Comparison Databricks vs. Google BigQuery vs. Oracle NoSQL vs. TigerGraph

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Graph DBMS

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

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.databricks.com

cloud.google.com/bigquery

www.oracle.com/database/nosql/technologies/nosql

www.tigergraph.com

Technical documentation

docs.databricks.com

cloud.google.com/bigquery/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.tigergraph.com

Developer

Databricks

Google

Oracle

Initial release

2013

2010

2011

2017

Current release

23.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

C++

Server operating systems

hosted

Linux
Solaris SPARC/x86

Linux

Data scheme

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

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

RESTful HTTP API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Python
R
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

configurable

ACID within a storage node (=shard)

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

off heap cache

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 and roles

Role-based access control

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.