DBMS > Prometheus vs. Riak TS vs. Vitess vs. Yaacomo

System Properties Comparison Prometheus vs. Riak TS vs. Vitess vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Open-source Time Series DBMS and monitoring system

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

Scalable, distributed, cloud-native DBMS, extending MySQL

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

prometheus.io

vitess.io

yaacomo.com

Technical documentation

prometheus.io/docs

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

vitess.io/docs

Developer

Open Source, formerly Basho Technologies

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2015

2013

2009

Current release

3.0.0, September 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0, commercial licenses available

commercial

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

Erlang

Server operating systems

Linux
Windows

Linux
OS X

Docker
Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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.

Import of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes, limited

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

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

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

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

Server-side scripts

Stored procedures

Erlang

yes

proprietary syntax

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by Federation

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

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

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

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

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

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page