DBMS > Amazon Redshift vs. Dgraph vs. H2GIS vs. MarkLogic vs. OrigoDB

System Properties Comparison Amazon Redshift vs. Dgraph vs. H2GIS vs. MarkLogic vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

Spatial extension of H2

Operational and transactional Enterprise NoSQL database

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Graph DBMS

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Object oriented DBMS

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

www.h2gis.org/docs/home

docs.marklogic.com

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

CNRS

MarkLogic Corp.

Robert Friberg et al

Initial release

2012

2016

2013

2001

2009

under the name LiveDB

Current release

11.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

LGPL 3.0

commercial

restricted free version is available

Open Source

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

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
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

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

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

Java

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

based on H2

yes

via XQuery or JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

yes

based on H2

yes

Source-replica replication

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

yes

depending on model

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Write ahead log

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

User concepts

Access control

fine grained access rights according to SQL-standard

Planned for future releases

yes

based on H2

Role-based access control at the document and subdocument levels

Role based authorization

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.