DBMS > Amazon DocumentDB vs. Ingres vs. OrientDB vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. Ingres vs. OrientDB 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

Well established RDBMS

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

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

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	4.11
Rank	#81	Overall
	#44	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

aws.amazon.com/documentdb

www.actian.com/databases/ingres

orientdb.org

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

docs.actian.com/ingres

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

docs.snowflake.net/manuals/index.html

Developer

Actian Corporation

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2019

1974

originally developed at University Berkely in early 1970s

2010

2014

Current release

11.2, May 2022

3.2.29, March 2024

License

Commercial or Open Source

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

Java

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language, no joins

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
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

Java, Javascript

user defined functions

Triggers

yes

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

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

Ingres Replicator

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

could be achieved with distributed queries

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

relationship in graphs

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

MVCC

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.

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

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.