DBMS > Amazon DynamoDB vs. Graph Engine vs. H2GIS vs. Microsoft Access vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. Graph Engine vs. H2GIS vs. Microsoft Access vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

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.)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Graph DBMS
Key-value store

Spatial DBMS

Relational DBMS

Graph DBMS

Secondary database models

Relational DBMS

Document store
RDF store

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/dynamodb

www.graphengine.io

www.h2gis.org

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

terminusdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

www.graphengine.io/docs/manual

www.h2gis.org/docs/home

developer.microsoft.com/en-us/access

terminusdb.github.io/terminusdb/#

Developer

Amazon

Microsoft

CNRS

Microsoft

DataChemist Ltd.

Initial release

2012

2010

2013

1992

2018

Current release

1902 (16.0.11328.20222), March 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

Open Source

LGPL 3.0

commercial

Bundled with Microsoft Office

Open Source

GPL V3

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

Java

C++

Prolog, Rust

Server operating systems

hosted

.NET

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Java

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript
Python

Server-side scripts

Stored procedures

yes

based on H2

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

by integration with AWS Lambda

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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

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

yes

but no files for transaction logging

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

yes

based on H2

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

Role-based access control

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.