DBMS > Amazon DynamoDB vs. Apache Drill vs. MarkLogic vs. Sequoiadb

System Properties Comparison Amazon DynamoDB vs. Apache Drill vs. MarkLogic vs. Sequoiadb

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Operational and transactional Enterprise NoSQL database

NewSQL database with distributed OLTP and SQL

Primary database model

Document store
Key-value store

Document store
Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Relational 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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

aws.amazon.com/dynamodb

drill.apache.org

www.marklogic.com

www.sequoiadb.com

Technical documentation

docs.aws.amazon.com/dynamodb

drill.apache.org/docs

docs.marklogic.com

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Amazon

Apache Software Foundation

MarkLogic Corp.

Sequoiadb Ltd.

Initial release

2012

2001

2013

Current release

1.20.3, January 2023

11.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

Server: AGPL; Client: Apache V2

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

Linux

Data scheme

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL SELECT statement is SQL:2003 compliant

yes

SQL92

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
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

proprietary protocol using JSON

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

via XQuery or JavaScript

JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

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)

Depending on the underlying data source

Role-based access control at the document and subdocument levels

simple password-based access control

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.