DBMS > GeoMesa vs. Tkrzw vs. Yaacomo vs. Yanza

System Properties Comparison GeoMesa vs. Tkrzw vs. Yaacomo vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Time Series DBMS for IoT Applications

Primary database model

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.geomesa.org

dbmx.net/tkrzw

yaacomo.com

yanza.com

Technical documentation

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

Developer

CCRi and others

Mikio Hirabayashi

Q2WEB GmbH

Yanza

Initial release

2014

2020

2009

2015

Current release

5.0.0, May 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Android
Linux
Windows

Windows

Data scheme

yes

schema-free

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

yes

APIs and other access methods

JDBC
ODBC

HTTP API

Supported programming languages

C++
Java
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.