DBMS > Databricks vs. HBase vs. Snowflake

System Properties Comparison Databricks vs. HBase 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.

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Primary database model

Document store
Relational DBMS

Wide column store

Relational 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	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.databricks.com

hbase.apache.org

www.snowflake.com

Technical documentation

docs.databricks.com

hbase.apache.org/book.html

docs.snowflake.net/manuals/index.html

Developer

Databricks

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Snowflake Computing Inc.

Initial release

2013

2008

2014

Current release

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

hosted

Data scheme

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

schema-free, schema definition possible

yes

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

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

Java API
RESTful HTTP API
Thrift

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Coprocessors in Java

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

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

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.