DBMS > FatDB vs. HEAVY.AI vs. Kinetica vs. OrientDB vs. Snowflake

System Properties Comparison FatDB vs. HEAVY.AI vs. Kinetica vs. OrientDB vs. Snowflake

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Fully vectorized database across both GPUs and CPUs

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.kinetica.com

orientdb.org

www.snowflake.com

Technical documentation

docs.heavy.ai

docs.kinetica.com

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

Developer

FatCloud

HEAVY.AI, Inc.

Kinetica

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2012

2016

2012

2010

2014

Current release

5.10, January 2022

7.1, August 2021

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

Apache version 2

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

Java

Server operating systems

Windows

Linux

All OS with a Java JDK (>= JDK 6)

hosted

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

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

Typing

predefined data types such as float or date

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

Via inetgration in SQL Server

yes

SQL-like DML and DDL statements

SQL-like query language, no joins

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Java, Javascript

user defined functions

Triggers

yes

via applications

yes

triggers when inserted values for one or more columns fall within a specified range

Hooks

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

selectable replication factor

Multi-source replication

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship 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

GPU vRAM or System RAM

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Access rights for users and roles; record level security configurable

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.