DBMS > IRONdb vs. JaguarDB vs. MySQL vs. VictoriaMetrics

System Properties Comparison IRONdb vs. JaguarDB vs. MySQL vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

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

Primary database model

Time Series DBMS

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.circonus.com/solutions/time-series-database/

www.jaguardb.com

www.mysql.com

victoriametrics.com

Technical documentation

docs.circonus.com/irondb/category/getting-started

www.jaguardb.com/support.html

dev.mysql.com/doc

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

Developer

Circonus LLC.

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

VictoriaMetrics

Initial release

2017

2015

1995

2018

Current release

V0.10.20, January 2018

3.3 July 2023

8.4.0, April 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

C and C++

C++

the server part. Clients available in other languages

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

yes, in Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication

Multi-source replication
Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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.

yes

User concepts

Access control

rights management via user accounts

Users with fine-grained authorization concept

no user groups or 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.