DBMS > GeoMesa vs. MonetDB vs. Sadas Engine vs. ToroDB vs. VictoriaMetrics

System Properties Comparison GeoMesa vs. MonetDB vs. Sadas Engine vs. ToroDB vs. VictoriaMetrics

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 relational database management system that stores data in columns

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A MongoDB-compatible JSON document store, built on top of PostgreSQL

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.geomesa.org

www.monetdb.org

www.sadasengine.com

github.com/torodb/server

victoriametrics.com

Technical documentation

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

www.monetdb.org/Documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

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

Developer

CCRi and others

MonetDB BV

SADAS s.r.l.

8Kdata

VictoriaMetrics

Initial release

2014

2004

2006

2016

2018

Current release

4.0.5, February 2024

Dec2023 (11.49), December 2023

8.0

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Mozilla Public License 2.0

commercial

free trial version available

Open Source

AGPL-V3

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

C++

Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL 2003 with some extensions

yes

APIs and other access methods

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

JDBC
ODBC
Proprietary protocol

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

Supported programming languages

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes, in SQL, C, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding via remote tables

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication available in experimental status

none

Source-replica replication

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

yes

managed by 'Learn by Usage'

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

In 2024 the MonetDB Foundation was established for the preservation, maintenance and further development of the ...
31 January 2024, Centrum Wiskunde & Informatica (CWI)

MonetDB Secures Investment From (and Partners With) ServiceNow
9 December 2021, Datanami

PostgreSQL, MonetDB, and Too-Big-for-Memory Data in R - Part I - DataScienceCentral.com
6 April 2018, Data Science Central

Test of Time Award for paper on vectorized execution
16 January 2024, Centrum Wiskunde & Informatica (CWI)

How MonetDB Exploits Modern CPU Performance | by Dwi Prasetyo Adi Nugroho
14 January 2020, Towards Data Science

provided by Google News

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

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

Green coding - VictoriaMetrics: The efficiency vs complexity trade-off
15 May 2024, ComputerWeekly.com

How VictoriaMetrics' open source approach led to mass industry adoption
3 May 2024, Tech.eu

VictoriaMetrics Machine Learning takes monitoring to the next level
19 March 2024, businesswire.com

provided by Google News

Share this page