DBMS > Databricks vs. HarperDB vs. Kinetica vs. Snowflake

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series 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	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.databricks.com

docs.harperdb.io/docs

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

Databricks

HarperDB

Kinetica

Snowflake Computing Inc.

Initial release

2013

2017

2012

2014

Current release

3.1, August 2021

7.1, August 2021

License

Commercial or Open Source

commercial

free community edition available

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

Node.js

C, C++

Server operating systems

hosted

Linux
OS X

Linux

hosted

Data scheme

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

dynamic schema

yes

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

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

Custom Functions

since release 3.1

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

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

yes

GPU vRAM or System RAM

User concepts

Access control

Access rights for users and roles

Access rights for users and roles on table level

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.