DBMS > IRONdb vs. Prometheus vs. SAP HANA vs. Yanza

System Properties Comparison IRONdb vs. Prometheus vs. SAP HANA vs. Yanza

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.

Yanza 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 Time Series DBMS and monitoring system

In-memory, column based data store. Available as appliance or cloud service

Time Series DBMS for IoT Applications

Primary database model

Time Series DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

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

prometheus.io

www.sap.com/products/hana.html

yanza.com

Technical documentation

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

prometheus.io/docs

help.sap.com/hana

Developer

Circonus LLC.

SAP

Yanza

Initial release

2017

2015

2010

2015

Current release

V0.10.20, January 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

Linux

Linux
Windows

Appliance or cloud-service

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

SQL

Support of SQL

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

yes

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

HTTP API

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++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes, in Lua

SQLScript, R

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

by Federation

yes

none

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

yes

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.