DBMS > Databricks vs. Dolt vs. MaxDB vs. Snowflake

System Properties Comparison Databricks vs. Dolt vs. MaxDB vs. Snowflake

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.

A MySQL compatible DBMS with Git-like versioning of data and schema

A robust and reliable RDBMS optimized to run all major SAP solutions

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store

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.02
Rank	#191	Overall
	#89	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.databricks.com

github.com/dolthub/dolt
www.dolthub.com

maxdb.sap.com

www.snowflake.com

Technical documentation

docs.databricks.com

docs.dolthub.com

maxdb.sap.com/documentation

docs.snowflake.net/manuals/index.html

Developer

Databricks

DoltHub Inc

SAP, acquired from Software AG (Adabas-D) in 1997

Snowflake Computing Inc.

Initial release

2013

2018

1984

2014

Current release

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Limited community 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

C++

Server operating systems

hosted

Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

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

yes

support of semi-structured data formats (JSON, XML, Avro)

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

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
WebDAV

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

currently in alpha release

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of 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.

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.