DBMS > HEAVY.AI vs. Hypertable vs. jBASE vs. Kinetica vs. Snowflake

System Properties Comparison HEAVY.AI vs. Hypertable vs. jBASE vs. Kinetica vs. Snowflake

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

An open source BigTable implementation based on distributed file systems such as Hadoop

A robust multi-value DBMS comprising development tools and middleware

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.kinetica.com

www.snowflake.com

Technical documentation

docs.heavy.ai

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Hypertable Inc.

Rocket Software (formerly Zumasys)

Kinetica

Snowflake Computing Inc.

Initial release

2016

2009

1991

2012

2014

Current release

5.10, January 2022

0.9.8.11, March 2016

5.7

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GNU version 3. Commercial license 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

C++ and CUDA

C++

C, C++

Server operating systems

Linux

Linux
OS X
Windows

an inofficial Windows port is available

AIX
Linux
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

C++ API
Thrift

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
Perl
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor on file system level

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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

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.