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

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

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.

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Key-value store

Native XML DBMS

Spatial DBMS

Relational DBMS

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	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

aws.amazon.com/dynamodb

basex.org

www.geomesa.org

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/dynamodb

docs.basex.org

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

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon

BaseX GmbH

CCRi and others

TmaxSoft

Initial release

2012

2007

2014

2003

Current release

10.7, August 2023

4.0.5, February 2024

6, April 2015

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

commercial

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

C and Assembler

Server operating systems

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

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.

yes

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Persistent Stored Procedure (PSM)

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

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

depending on storage layer

Multi-source replication
Source-replica 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

Immediate Consistency

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.

depending on storage layer

planned for next version

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.