DBMS > Databricks vs. Datomic vs. Google BigQuery vs. Linter

System Properties Comparison Databricks vs. Datomic vs. Google BigQuery vs. Linter

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.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Spatial 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	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Website

www.databricks.com

www.datomic.com

cloud.google.com/bigquery

linter.ru

Technical documentation

docs.databricks.com

docs.datomic.com

cloud.google.com/bigquery/docs

Developer

Databricks

Cognitect

Google

relex.ru

Initial release

2013

2012

2010

1990

Current release

1.0.7075, December 2023

License

Commercial or Open Source

commercial

limited edition free

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, Clojure

C and C++

Server operating systems

hosted

All OS with a Java VM

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

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

yes

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

Python
R
Scala

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Transaction Functions

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.