DBMS > Amazon DynamoDB vs. GeoMesa vs. Heroic vs. Microsoft Azure Synapse Analytics vs. Warp 10

System Properties Comparison Amazon DynamoDB vs. GeoMesa vs. Heroic vs. Microsoft Azure Synapse Analytics vs. Warp 10

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Key-value store

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/dynamodb

www.geomesa.org

github.com/spotify/heroic

azure.microsoft.com/services/synapse-analytics

www.warp10.io

Technical documentation

docs.aws.amazon.com/dynamodb

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

spotify.github.io/heroic

docs.microsoft.com/azure/synapse-analytics

www.warp10.io/content/02_Getting_started

Developer

Amazon

CCRi and others

Spotify

Microsoft

SenX

Initial release

2012

2014

2016

2015

Current release

4.0.5, February 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache License 2.0

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

C++

Java

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
PHP

Server-side scripts

Stored procedures

Transact SQL

yes

WarpScript

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

selectable replication factor

based on HBase

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.