DBMS > AnzoGraph DB vs. HEAVY.AI vs. Netezza vs. Snowflake vs. STSdb

System Properties Comparison AnzoGraph DB vs. HEAVY.AI vs. Netezza vs. Snowflake vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Data warehouse and analytics appliance part of IBM PureSystems

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

Graph DBMS
RDF store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Website

cambridgesemantics.com/anzograph

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

www.ibm.com/products/netezza

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.heavy.ai

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

HEAVY.AI, Inc.

IBM

Snowflake Computing Inc.

STS Soft SC

Initial release

2018

2016

2000

2014

2011

Current release

2.3, January 2021

5.10, January 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

free trial version available

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

Server operating systems

Linux

included in appliance

hosted

Windows

Data scheme

Schema-free and OWL/RDFS-schema support

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

C++
Java
Python

All languages supporting JDBC/ODBC/Thrift
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Round robin

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.