DBMS > GeoMesa vs. gStore

System Properties Comparison GeoMesa vs. gStore

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and gStore with Apache Ignite.

Editorial information provided by DB-Engines

Name

Description

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

A native Graph DBMS to store and maintain very large RDF datasets.

Primary database model

Spatial DBMS

Graph DBMS
RDF store

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

Score	0.74
Rank	#215	Overall
	#4	Spatial DBMS

Score	0.04
Rank	#362	Overall
	#37	Graph DBMS
	#18	RDF stores

Website

www.geomesa.org

en.gstore.cn

Technical documentation

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

en.gstore.cn/#/enDocs

Developer

CCRi and others

Initial release

2014

2016

Current release

5.0.1, July 2024

1.2, November 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

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

C++

Server operating systems

Linux

Data scheme

yes

schema-free and OWL/RDFS-schema support

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

HTTP API
SPARQL 1.1

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

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

yes

depending on the DBMS used for storage

Users, roles and permissions, Role-Based Access Control (RBAC) supported

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.