DBMS > Atos Standard Common Repository vs. Blueflood vs. IRONdb vs. SQLite vs. VictoriaMetrics

System Properties Comparison Atos Standard Common Repository vs. Blueflood vs. IRONdb vs. SQLite vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Scalable TimeSeries DBMS based on Cassandra

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

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Time Series DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

blueflood.io

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

www.sqlite.org

victoriametrics.com

Technical documentation

github.com/rax-maas/blueflood/wiki

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

www.sqlite.org/docs.html

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

Developer

Atos Convergence Creators

Rackspace

Circonus LLC.

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2016

2013

2017

2000

2018

Current release

1703

V0.10.20, January 2018

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Java

C and C++

Server operating systems

Linux

Linux
OS X

Linux

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

Schema and schema-less with LDAP views

predefined scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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)

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

HTTP REST

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Supported programming languages

All languages with LDAP bindings

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

configurable replication factor, datacenter aware

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

LDAP bind authentication

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.