DBMS > GeoMesa vs. Tkrzw

System Properties Comparison GeoMesa vs. Tkrzw

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and Tkrzw with Neo4j.

Editorial information provided by DB-Engines

Name

Description

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Spatial DBMS

Key-value store

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

www.geomesa.org

dbmx.net/tkrzw

Technical documentation

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

Developer

CCRi and others

Mikio Hirabayashi

Initial release

2014

2020

Current release

4.0.5, February 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 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

Scala

C++

Server operating systems

Linux
macOS

Data scheme

yes

schema-free

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

Supported programming languages

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Triggers

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

yes

using specific database classes

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.