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

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

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

Document store
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	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Website

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

linter.ru

planetscale.com

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

docs.heavy.ai

planetscale.com/docs

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

relex.ru

PlanetScale

Snowflake Computing Inc.

STS Soft SC

Initial release

2016

1990

2020

2014

2011

Current release

5.10, January 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPLv2, commercial license available

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

Server operating systems

Linux

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

Docker
Linux
macOS

hosted

Windows

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)

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

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.