DBMS > Amazon DynamoDB vs. Apache IoTDB vs. GeoMesa vs. OrigoDB

System Properties Comparison Amazon DynamoDB vs. Apache IoTDB vs. GeoMesa vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Time Series DBMS

Spatial DBMS

Document store
Object oriented DBMS

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

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

aws.amazon.com/dynamodb

iotdb.apache.org

www.geomesa.org

origodb.com

Technical documentation

docs.aws.amazon.com/dynamodb

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

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

origodb.com/docs

Developer

Amazon

Apache Software Foundation

CCRi and others

Robert Friberg et al

Initial release

2012

2018

2014

2009

under the name LiveDB

Current release

1.1.0, April 2023

5.0.1, July 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

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

Scala

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

Linux
Windows

Data scheme

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

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC
Native API

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
Python
Scala

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

depending on storage layer

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Strong Consistency with Raft

depending on storage layer

Foreign keys

Referential integrity

depending on model

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

Write ahead log

In-memory capabilities

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

yes

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

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.