DBMS > Amazon Redshift vs. Dgraph vs. H2GIS vs. Microsoft Access vs. OrigoDB

System Properties Comparison Amazon Redshift vs. Dgraph vs. H2GIS vs. Microsoft Access 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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A fully ACID in-memory object graph database

Primary database model

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	101.16
Rank	#11	Overall
	#8	Relational DBMS

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

Website

aws.amazon.com/redshift

dgraph.io

www.h2gis.org

www.microsoft.com/en-us/microsoft-365/access

origodb.com

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

www.h2gis.org/docs/home

developer.microsoft.com/en-us/access

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

CNRS

Microsoft

Robert Friberg et al

Initial release

2012

2016

2013

1992

2009

under the name LiveDB

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

LGPL 3.0

commercial

Bundled with Microsoft Office

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

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Data scheme

yes

schema-free

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.

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
DAO
ODBC
OLE DB

.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++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

based on H2

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

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

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Planned for future releases

yes

based on H2

a simple user-level security was built in till version Access 2003

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.