DBMS > HEAVY.AI vs. MarkLogic vs. MonetDB vs. Snowflake

System Properties Comparison HEAVY.AI vs. MarkLogic vs. MonetDB vs. Snowflake

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

Operational and transactional Enterprise NoSQL database

A relational database management system that stores data in columns

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

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

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	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.marklogic.com

www.monetdb.org

www.snowflake.com

Technical documentation

docs.heavy.ai

docs.marklogic.com

www.monetdb.org/Documentation

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

MarkLogic Corp.

MonetDB BV

Snowflake Computing Inc.

Initial release

2016

2001

2004

2014

Current release

5.10, January 2022

11.0, December 2022

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Open Source

Mozilla Public License 2.0

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

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced

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

yes

SQL92

yes

SQL 2003 with some extensions

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes, in SQL, C, R

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Sharding via remote tables

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

Source-replica replication available in experimental status

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

fine grained access rights according to SQL-standard

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.