DBMS > HEAVY.AI vs. Microsoft Azure Table Storage vs. MySQL vs. NSDb

System Properties Comparison HEAVY.AI vs. Microsoft Azure Table Storage vs. MySQL vs. NSDb

Please select another system to include it in the comparison.

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

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

www.mysql.com

nsdb.io

Technical documentation

docs.heavy.ai

dev.mysql.com/doc

nsdb.io/Architecture

Developer

HEAVY.AI, Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2012

1995

2017

Current release

5.10, January 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC
Thrift
Vega

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
HTTP REST
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Java
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

optimistic locking

ACID

not for MyISAM storage engine

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

Using Apache Lucene

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

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

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.