DBMS > Amazon DocumentDB vs. GeoMesa vs. Sadas Engine vs. ToroDB vs. VictoriaMetrics

System Properties Comparison Amazon DocumentDB vs. GeoMesa 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

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

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

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

aws.amazon.com/documentdb

www.geomesa.org

www.sadasengine.com

github.com/torodb/server

victoriametrics.com

Technical documentation

aws.amazon.com/documentdb/resources

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

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

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

Developer

CCRi and others

SADAS s.r.l.

8Kdata

VictoriaMetrics

Initial release

2019

2014

2006

2016

2018

Current release

4.0.5, February 2024

8.0

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 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

yes

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

hosted

AIX
Linux
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

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

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
Proprietary protocol

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

depending on storage layer

none

Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

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

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

Access rights for users and roles

yes

depending on the DBMS used for storage

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

Use LangChain and vector search on Amazon DocumentDB to build a generative AI chatbot | Amazon Web Services
20 May 2024, AWS Blog

AWS announces Amazon DocumentDB zero-ETL integration with Amazon OpenSearch Service
16 May 2024, AWS Blog

Vector search for Amazon DocumentDB (with MongoDB compatibility) is now generally available | Amazon Web Services
29 November 2023, AWS Blog

AWS announces Amazon DocumentDB I/O-Optimized
21 November 2023, AWS Blog

Use headless clusters in Amazon DocumentDB for cost-effective multi-Region resiliency | Amazon Web Services
8 March 2024, AWS Blog

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