DBMS > BaseX vs. GeoMesa

System Properties Comparison BaseX vs. GeoMesa

Please select another system to include it in the comparison.

Our visitors often compare BaseX and GeoMesa with MongoDB, Elasticsearch and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

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.

Primary database model

Native XML DBMS

Spatial DBMS

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

Score	1.90
Rank	#136	Overall
	#4	Native XML DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Website

basex.org

www.geomesa.org

Technical documentation

docs.basex.org

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

Developer

BaseX GmbH

CCRi and others

Initial release

2007

2014

Current release

10.7, August 2023

4.0.5, February 2024

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

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

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

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

Server-side scripts

Stored procedures

yes

Triggers

yes

via events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

multiple readers, single writer

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

Users with fine-grained authorization concept on 4 levels

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

XML Injection Attacks: What to Know About XPath, XQuery, XXE & More
18 May 2022, Hashed Out by The SSL Store™

9 Skills You Need to Become a Data Engineer
2 November 2022, KDnuggets

provided by Google News

Share this page