DBMS > Amazon DynamoDB vs. CrateDB vs. EsgynDB vs. GeoMesa

System Properties Comparison Amazon DynamoDB vs. CrateDB vs. EsgynDB vs. GeoMesa

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

Distributed Database based on Lucene

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Primary database model

Document store
Key-value store

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Relational 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	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Website

aws.amazon.com/dynamodb

cratedb.com

www.esgyn.cn

www.geomesa.org

Technical documentation

docs.aws.amazon.com/dynamodb

cratedb.com/docs

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

Developer

Amazon

Crate

Esgyn

CCRi and others

Initial release

2012

2013

2015

2014

Current release

5.8.1, August 2024

5.0.1, July 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

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

Java

C++, Java

Scala

Server operating systems

hosted

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, 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

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions (Javascript)

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

Multi-source replication between multi datacenters

depending on storage layer

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

Eventual Consistency
Read-after-write consistency on record level

Immediate Consistency

depending on storage layer

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

User concepts

Access control

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

rights management via user accounts

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.