DBMS > GeoMesa vs. MySQL vs. Sadas Engine vs. VictoriaMetrics

System Properties Comparison GeoMesa vs. MySQL vs. Sadas Engine vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

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

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

Primary database model

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

Technical documentation

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

dev.mysql.com/doc

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

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

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

SADAS s.r.l.

VictoriaMetrics

Initial release

2014

1995

2006

2018

Current release

5.0.0, May 2024

8.4.0, April 2024

8.0

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free trial version available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
Proprietary protocol

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

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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

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.