DBMS > Apache Druid vs. BaseX vs. GeoMesa vs. RDF4J vs. SAP HANA

System Properties Comparison Apache Druid vs. BaseX vs. GeoMesa vs. RDF4J vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

druid.apache.org/docs/latest/design

docs.basex.org

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

rdf4j.org/documentation

help.sap.com/hana

Developer

Apache Software Foundation and contributors

BaseX GmbH

CCRi and others

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

SAP

Initial release

2012

2007

2014

2004

2010

Current release

29.0.1, April 2024

10.7, August 2023

4.0.5, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD license

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Java

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

yes

schema-less columns are supported

schema-free

yes

RDF Schemas

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.

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
Haskell
Java
JavaScript

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Users with fine-grained authorization concept on 4 levels

yes

depending on the DBMS used for storage

yes

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.