DBMS > GeoMesa vs. RDF4J

System Properties Comparison GeoMesa vs. RDF4J

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and RDF4J with PostgreSQL, Neo4j and MongoDB.

Editorial information provided by DB-Engines

Name

Description

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.

Primary database model

Spatial DBMS

RDF store

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

www.geomesa.org

rdf4j.org

Technical documentation

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

rdf4j.org/documentation

Developer

CCRi and others

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

Initial release

2014

2004

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.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

Scala

Java

Server operating systems

Linux
OS X
Unix
Windows

Data scheme

yes

RDF Schemas

Typing

predefined data types such as float or date

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
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page