DBMS > Amazon DynamoDB vs. GeoMesa vs. H2GIS vs. PouchDB vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. GeoMesa vs. H2GIS vs. PouchDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Spatial extension of H2

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Document store
Key-value store

Spatial DBMS

Document store

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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

www.geomesa.org/documentation/stable/user/index.html

www.h2gis.org/docs/home

pouchdb.com/guides

terminusdb.github.io/terminusdb/#

Developer

Amazon

CCRi and others

CNRS

Apache Software Foundation

DataChemist Ltd.

Initial release

2012

2014

2013

2012

2018

Current release

5.0.0, May 2024

7.1.1, June 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache License 2.0

Open Source

LGPL 3.0

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

Scala

Java

JavaScript

Prolog, Rust

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

schema-free

yes

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

via views

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

JavaScript

JavaScript
Python

Server-side scripts

Stored procedures

yes

based on H2

View functions in JavaScript

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

with a proxy-based framework, named couchdb-lounge

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

based on H2

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

depending on storage layer

Immediate Consistency

Eventual 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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

in-memory journaling

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

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

yes

depending on the DBMS used for storage

yes

based on H2

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.