DBMS > Amazon DocumentDB vs. Datomic vs. EXASOL vs. HEAVY.AI vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. Datomic vs. EXASOL vs. HEAVY.AI vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

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

Primary database model

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/documentdb

www.datomic.com

www.exasol.com

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

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

docs.datomic.com

www.exasol.com/resources

docs.heavy.ai

docs.snowflake.net/manuals/index.html

Developer

Cognitect

Exasol

HEAVY.AI, Inc.

Snowflake Computing Inc.

Initial release

2019

2012

2000

2016

2014

Current release

1.0.7075, December 2023

5.10, January 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache Version 2; enterprise edition available

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

Java, Clojure

C++ and CUDA

Server operating systems

hosted

All OS with a Java VM

Linux

hosted

Data scheme

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

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
Java

Java
Lua
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Round robin

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

none

But extensive use of caching in the application peers

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles according to SQL-standard

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.