DBMS > Amazon Redshift vs. Graph Engine vs. MarkLogic vs. XTDB

System Properties Comparison Amazon Redshift vs. Graph Engine vs. MarkLogic vs. XTDB

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Operational and transactional Enterprise NoSQL database

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

www.graphengine.io

www.marklogic.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

docs.marklogic.com

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Microsoft

MarkLogic Corp.

Juxt Ltd.

Initial release

2012

2010

2001

2019

Current release

11.0, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

restricted free version is available

Open Source

MIT License

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

.NET and C

C++

Clojure

Server operating systems

hosted

.NET

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

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

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

informational only, not enforced by the system

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.