DBMS > HEAVY.AI vs. Linter vs. Snowflake vs. STSdb vs. VoltDB

System Properties Comparison HEAVY.AI vs. Linter vs. Snowflake vs. STSdb vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

RDBMS for high security requirements

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

linter.ru

www.snowflake.com

github.com/STSSoft/STSdb4

www.voltdb.com

Technical documentation

docs.heavy.ai

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

HEAVY.AI, Inc.

relex.ru

Snowflake Computing Inc.

STS Soft SC

VoltDB Inc.

Initial release

2016

1990

2014

2011

2010

Current release

5.10, January 2022

4.0.8, September 2015

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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 and C++

Java, C++

Server operating systems

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Windows

Linux
OS X

for development

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

CLI Client
JDBC
ODBC

.NET Client API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript (Node.js)
Python

C#
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

Java

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

Users and roles with access to stored procedures

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.