DBMS > GeoMesa vs. Graphite

System Properties Comparison GeoMesa vs. Graphite

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and Graphite with Elasticsearch, Neo4j and InfluxDB.

Editorial information provided by DB-Engines

Name

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Spatial DBMS

Time Series DBMS

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

Score	0.80
Rank	#211	Overall
	#4	Spatial DBMS

Score	5.00
Rank	#63	Overall
	#4	Time Series DBMS

Website

www.geomesa.org

github.com/graphite-project/graphite-web

Technical documentation

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

graphite.readthedocs.io

Developer

CCRi and others

Chris Davis

Initial release

2014

2006

Current release

5.0.1, July 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 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

Python

Server operating systems

Linux
Unix

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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
Sockets

Supported programming languages

JavaScript (Node.js)
Python

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

none

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

locking

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Try out the Graphite monitoring tool for time-series data
29 October 2019, TechTarget

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

The Billion Data Point Challenge: Building a Query Engine for High Cardinality Time Series Data
10 December 2018, Uber

Grafana Labs Announces Mimir Time Series Database
1 April 2022, Datanami

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google News

Share this page