DBMS > IRONdb vs. RavenDB vs. RocksDB vs. VictoriaMetrics

System Properties Comparison IRONdb vs. RavenDB vs. RocksDB 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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

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

ravendb.net

rocksdb.org

victoriametrics.com

Technical documentation

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

ravendb.net/docs

github.com/facebook/rocksdb/wiki

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

Developer

Circonus LLC.

Hibernating Rhinos

Facebook, Inc.

VictoriaMetrics

Initial release

2017

2010

2013

2018

Current release

V0.10.20, January 2018

5.4, July 2022

8.11.4, April 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

BSD

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.

Implementation language

C and C++

C++

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

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

SQL-like query language (RQL)

APIs and other access methods

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java 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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication

yes

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

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.

yes

User concepts

Access control

Authorization levels configured per client per database

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.