DBMS > Amazon DynamoDB vs. Citus vs. GeoMesa vs. HugeGraph

System Properties Comparison Amazon DynamoDB vs. Citus vs. GeoMesa vs. HugeGraph

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

A fast-speed and highly-scalable Graph DBMS

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Graph DBMS

Secondary database models

Document store

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

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Website

aws.amazon.com/dynamodb

www.citusdata.com

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.citusdata.com

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

hugegraph.apache.org/docs

Developer

Amazon

CCRi and others

Baidu

Initial release

2012

2010

2014

2018

Current release

8.1, December 2018

4.0.5, February 2024

0.9

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

AGPL, commercial license also available

Open Source

Apache License 2.0

Open Source

Apache Version 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

Server operating systems

hosted

Linux

Linux
macOS
Unix

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

also supports composite index and range index

SQL

Support of SQL

yes

standard, with numerous extensions

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Groovy
Java
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

asynchronous Gremlin script jobs

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

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)

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Users, roles and permissions

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.