DBMS > Drizzle vs. HEAVY.AI vs. Kinetica vs. SAP HANA vs. Snowflake

System Properties Comparison Drizzle vs. HEAVY.AI vs. Kinetica vs. SAP HANA vs. Snowflake

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

www.sap.com/products/hana.html

www.snowflake.com

Technical documentation

docs.heavy.ai

docs.kinetica.com

help.sap.com/hana

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

HEAVY.AI, Inc.

Kinetica

SAP

Snowflake Computing Inc.

Initial release

2008

2016

2012

2010

2014

Current release

7.2.4, September 2012

5.10, January 2022

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; enterprise edition available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++ and CUDA

C, C++

Server operating systems

FreeBSD
Linux
OS X

Linux

Appliance or cloud-service

hosted

Data scheme

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

yes

with proprietary extensions

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

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

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

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

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

GPU vRAM or System RAM

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

yes

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

More information provided by the system vendor

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.