DBMS > Cachelot.io vs. GeoMesa vs. Prometheus

System Properties Comparison Cachelot.io vs. GeoMesa vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Open-source Time Series DBMS and monitoring system

Primary database model

Key-value store

Spatial DBMS

Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

cachelot.io

www.geomesa.org

prometheus.io

Technical documentation

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

prometheus.io/docs

Developer

CCRi and others

Initial release

2015

2014

2015

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

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

C++

Scala

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

Data scheme

schema-free

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.

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

Memcached protocol

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

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

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

Exadata Real-Time Insight - Quick Start
3 April 2024, Oracle

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

Consider Grafana vs. Prometheus for your time-series tools
18 October 2021, TechTarget

provided by Google News

Share this page