DBMS > Amazon DocumentDB vs. Apache Phoenix vs. DataFS vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. Apache Phoenix vs. DataFS vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Primary database model

Secondary database models

Graph DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/documentdb

phoenix.apache.org

newdatabase.com

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

phoenix.apache.org

dev.mobiland.com/Overview.xsp

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Mobiland AG

Snowflake Computing Inc.

Initial release

2019

2014

2018

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

1.1.263, October 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 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

Java

Server operating systems

hosted

Linux
Unix
Windows

Windows

hosted

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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)

JDBC

.NET Client API
Proprietary client DLL
WinRT client

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
VB.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

no, except callback-events from server when changes happened

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Proprietary Sharding system

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

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Windows-Profile

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.