DBMS > Amazon Redshift vs. MarkLogic vs. Microsoft Azure SQL Database vs. Quasardb

System Properties Comparison Amazon Redshift vs. MarkLogic vs. Microsoft Azure SQL Database vs. Quasardb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Operational and transactional Enterprise NoSQL database

Database as a Service offering with high compatibility to Microsoft SQL Server

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Website

aws.amazon.com/redshift

www.progress.com/marklogic

azure.microsoft.com/en-us/products/azure-sql/database

quasar.ai

Technical documentation

docs.aws.amazon.com/redshift

www.progress.com/marklogic/documentation

docs.microsoft.com/en-us/azure/azure-sql

doc.quasar.ai/master

Developer

Amazon (based on PostgreSQL)

MarkLogic Corp.

Microsoft

quasardb

Initial release

2012

2001

2010

2009

Current release

11.0, December 2022

V12

3.14.1, January 2024

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Schema can be enforced

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

restricted

yes

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via XQuery or JavaScript

Transact SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

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

by using LevelDB

In-memory capabilities

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

yes

yes, with Range Indexes

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.