DBMS > HEAVY.AI vs. Microsoft Access vs. PouchDB vs. Snowflake

System Properties Comparison HEAVY.AI vs. Microsoft Access vs. PouchDB 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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

www.microsoft.com/en-us/microsoft-365/access

pouchdb.com

www.snowflake.com

Technical documentation

docs.heavy.ai

developer.microsoft.com/en-us/access

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Microsoft

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2016

1992

2012

2014

Current release

5.10, January 2022

1902 (16.0.11328.20222), March 2019

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Bundled with Microsoft Office

Open Source

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

JavaScript

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

yes

schema-free

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

via views

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

a simple user-level security was built in till version Access 2003

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.