DBMS > Amazon DynamoDB vs. BaseX vs. Dolt vs. Warp 10

System Properties Comparison Amazon DynamoDB vs. BaseX vs. Dolt vs. Warp 10

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.

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Primary database model

Document store
Key-value store

Native XML DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store

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	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/dynamodb

basex.org

github.com/dolthub/dolt
www.dolthub.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/dynamodb

docs.basex.org

docs.dolthub.com

www.warp10.io/content/02_Getting_started

Developer

Amazon

BaseX GmbH

DoltHub Inc

SenX

Initial release

2012

2007

2018

2015

Current release

11.0, June 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

BSD license

Open Source

Apache Version 2.0

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

Server operating systems

hosted

Linux
OS X
Windows

Linux
macOS
Windows

Linux
OS X
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

yes

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

CLI Client
HTTP REST

HTTP API
Jupyter
WebSocket

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

WarpScript

Triggers

yes

by integration with AWS Lambda

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

based on HBase

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

multiple readers, single writer

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.

yes

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

Only one user is configurable, and must be specified in the config file at startup

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.