DBMS > Amazon DynamoDB vs. BaseX vs. GeoMesa vs. RavenDB

System Properties Comparison Amazon DynamoDB vs. BaseX vs. GeoMesa vs. RavenDB

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store
Key-value store

Native XML DBMS

Spatial DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/dynamodb

basex.org

www.geomesa.org

ravendb.net

Technical documentation

docs.aws.amazon.com/dynamodb

docs.basex.org

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

ravendb.net/docs

Developer

Amazon

BaseX GmbH

CCRi and others

Hibernating Rhinos

Initial release

2012

2007

2014

2010

Current release

11.0, June 2024

5.0.0, May 2024

5.4, July 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

BSD license

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

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

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

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

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

depending on storage layer

Multi-source replication

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

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

multiple readers, single writer

ACID, Cluster-wide transaction available

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)

Users with fine-grained authorization concept on 4 levels

yes

depending on the DBMS used for storage

Authorization levels configured per client per database

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.