DBMS > GeoMesa vs. VictoriaMetrics

System Properties Comparison GeoMesa vs. VictoriaMetrics

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and VictoriaMetrics with Elasticsearch, PostgreSQL and MongoDB.

Editorial information provided by DB-Engines

Name

Description

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Spatial DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.geomesa.org

victoriametrics.com

Technical documentation

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

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

CCRi and others

VictoriaMetrics

Initial release

2014

2018

Current release

4.0.5, February 2024

v1.91, May 2023

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

Server operating systems

FreeBSD
Linux
macOS
OpenBSD

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

APIs and other access methods

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Server-side scripts

Stored procedures

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

Synchronous 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

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

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

OpenTelemetry Is Too Complicated, VictoriaMetrics Says
1 April 2024, Datanami

KubeCon24: VictoriaMetrics' Simpler Alternative to Prometheus
20 March 2024, The New Stack

VictoriaMetrics Machine Learning takes monitoring to the next level
19 March 2024, Business Wire

VictoriaMetrics takes organic growth over investor pressure
11 December 2023, The Register

VictoriaMetrics offers free open source monitoring
5 December 2023, ComputerWeekly.com

provided by Google News

Share this page