DBMS > GeoMesa vs. ToroDB vs. Transwarp ArgoDB

System Properties Comparison GeoMesa vs. ToroDB vs. Transwarp ArgoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB 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 MongoDB-compatible JSON document store, built on top of PostgreSQL

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Spatial DBMS

Document store

Relational DBMS

Secondary database models

Search engine

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.07
Rank	#350	Overall
	#153	Relational DBMS

Website

www.geomesa.org

github.com/torodb/server

www.transwarp.cn/en/product/argodb

Technical documentation

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

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

CCRi and others

8Kdata

Transwarp

Initial release

2014

2016

Current release

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

AGPL-V3

commercial

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

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

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

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles

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.