DBMS > MySQL vs. Riak TS vs. Trafodion vs. VictoriaMetrics

System Properties Comparison MySQL vs. Riak TS vs. Trafodion vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used open source RDBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Transactional SQL-on-Hadoop DBMS

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

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	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Score	1.42
Rank	#161	Overall
	#14	Time Series DBMS

Website

www.mysql.com

trafodion.apache.org

victoriametrics.com

Technical documentation

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/ts/latest

trafodion.apache.org/documentation.html

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

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Open Source, formerly Basho Technologies

Apache Software Foundation, originally developed by HP

VictoriaMetrics

Initial release

1995

2015

2014

2018

Current release

8.3.0, January 2024

3.0.0, September 2022

2.3.0, February 2019

v1.91, May 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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

C and C++

Erlang

C++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

with proprietary extensions

yes, limited

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

Erlang

Java Stored Procedures

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes, via HBase

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between datasets can be stored

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

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.

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights 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.