DBMS > Amazon DynamoDB vs. MarkLogic vs. Microsoft Azure AI Search vs. Snowflake

System Properties Comparison Amazon DynamoDB vs. MarkLogic vs. Microsoft Azure AI Search vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Operational and transactional Enterprise NoSQL database

Search-as-a-service for web and mobile app development

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

Primary database model

Document store
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Search engine

Relational DBMS

Secondary database models

Vector DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/dynamodb

www.marklogic.com

azure.microsoft.com/en-us/services/search

www.snowflake.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.marklogic.com

learn.microsoft.com/en-us/azure/search

docs.snowflake.net/manuals/index.html

Developer

Amazon

MarkLogic Corp.

Microsoft

Snowflake Computing Inc.

Initial release

2012

2001

2015

2014

Current release

11.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

restricted free version is 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

C++

Server operating systems

hosted

Linux
OS X
Windows

hosted

Data scheme

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

APIs and other access methods

RESTful HTTP API

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

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

user defined functions

Triggers

yes

by integration with AWS Lambda

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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, with Range Indexes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Role-based access control at the document and subdocument levels

yes

using Azure authentication

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.