DBMS > GeoMesa vs. TerminusDB

System Properties Comparison GeoMesa vs. TerminusDB

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and TerminusDB with Neo4j, DuckDB and MongoDB.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Spatial DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.80
Rank	#208	Overall
	#4	Spatial DBMS

Score	0.18
Rank	#320	Overall
	#29	Graph DBMS

Website

www.geomesa.org

terminusdb.com

Technical documentation

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

terminusdb.github.io/terminusdb/#

Developer

CCRi and others

DataChemist Ltd.

Initial release

2014

2018

Current release

5.0.0, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux

Data scheme

yes

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

SQL-like query language (WOQL)

APIs and other access methods

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Journaling Streams

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based access control

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

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source Critical Asset Management System (CAMS) to help cities become disaster and climate resilient
12 April 2022, United Nations Office for Disaster Risk Reduction

Bus Terminus Update – April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Share this page