DBMS > Amazon DynamoDB vs. GeoMesa vs. H2GIS vs. InterSystems Caché vs. Microsoft Azure Table Storage

System Properties Comparison Amazon DynamoDB vs. GeoMesa vs. H2GIS vs. InterSystems Caché vs. Microsoft Azure Table Storage

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

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

A multi-model DBMS and application server

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Document store
Key-value store

Spatial DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Wide column store

Secondary database models

Relational DBMS

Document 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	4.04
Rank	#77	Overall
	#6	Wide column stores

Website

aws.amazon.com/dynamodb

www.geomesa.org

www.h2gis.org

www.intersystems.com/products/cache

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.aws.amazon.com/dynamodb

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

www.h2gis.org/docs/home

docs.intersystems.com

Developer

Amazon

CCRi and others

CNRS

InterSystems

Microsoft

Initial release

2012

2014

2013

1997

2012

Current release

5.0.0, May 2024

2018.1.4, May 2020

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

commercial

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

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

depending on used data model

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

C#
C++
Java

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

Server-side scripts

Stored procedures

yes

based on H2

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

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

based on H2

Source-replica replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

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

Access rights for users, groups and roles

Access rights based on private key authentication or shared access signatures

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.