DBMS > FatDB vs. GeoMesa vs. Prometheus vs. RethinkDB

System Properties Comparison FatDB vs. GeoMesa vs. Prometheus vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Open-source Time Series DBMS and monitoring system

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Document store
Key-value store

Spatial DBMS

Time Series DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

www.geomesa.org

prometheus.io

rethinkdb.com

Technical documentation

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

prometheus.io/docs

rethinkdb.com/docs

Developer

FatCloud

CCRi and others

The Linux Foundation

since July 2017

Initial release

2012

2014

2015

2009

Current release

5.0.0, May 2024

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2

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

C++

Server operating systems

Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, binary, float, bool, date, geometry

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

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

Supported programming languages

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

yes

by Federation

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

yes

users and table-level permissions

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

Meet some database management systems you are likely to hear more about in the future
4 August 2014, Paul Andlinger

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

Exadata Real-Time Insight - Quick Start
3 April 2024, blogs.oracle.com

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

OpenTelemetry vs. Prometheus: You can’t fix what you can’t see
29 March 2024, ibm.com

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

provided by Google News

An introduction to building realtime apps with RethinkDB
9 July 2022, devmio

How to Use RethinkDB with Node.js Applications — SitePoint
16 December 2015, SitePoint

Stripe acquires team behind NoSQL database startup RethinkDB
5 October 2016, VentureBeat

MongoDB: The Popular Database for IoT
15 August 2023, Open Source For You

RethinkDB is dead, and MongoDB isn't what killed it
24 January 2017, TechRepublic

provided by Google News

Share this page