DBMS > Amazon DocumentDB vs. MarkLogic vs. Microsoft SQL Server vs. OpenEdge

System Properties Comparison Amazon DocumentDB vs. MarkLogic vs. Microsoft SQL Server vs. OpenEdge

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

Operational and transactional Enterprise NoSQL database

Microsofts flagship relational DBMS

Application development environment with integrated database management system

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

aws.amazon.com/documentdb

www.marklogic.com

www.microsoft.com/en-us/sql-server

www.progress.com/openedge

Technical documentation

aws.amazon.com/documentdb/resources

docs.marklogic.com

learn.microsoft.com/en-US/sql/sql-server

documentation.progress.com/output/ua/OpenEdge_latest

Developer

MarkLogic Corp.

Microsoft

Progress Software Corporation

Initial release

2019

2001

1989

1984

Current release

11.0, December 2022

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

restricted free version is available

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

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

Schema can be enforced

yes

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

close to SQL 92

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

yes, but depending on the SQL-Server Edition

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

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

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

yes

User concepts

Access control

Access rights for users and roles

Role-based access control at the document and subdocument levels

fine grained access rights according to SQL-standard

Users and groups

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.