DBMS > FatDB vs. IRONdb vs. Microsoft Azure Table Storage vs. Prometheus vs. Yaacomo

System Properties Comparison FatDB vs. IRONdb vs. Microsoft Azure Table Storage vs. Prometheus vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A Wide Column Store for rapid development using massive semi-structured datasets

Open-source Time Series DBMS and monitoring system

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

Primary database model

Document store
Key-value store

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

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

prometheus.io

yaacomo.com

Technical documentation

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

prometheus.io/docs

Developer

FatCloud

Circonus LLC.

Microsoft

Q2WEB GmbH

Initial release

2012

2017

2012

2015

2009

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

Windows

Linux

hosted

Linux
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

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

Via inetgration in SQL Server

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

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API

RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

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#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

via applications

yes, in Lua

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

configurable replication factor, datacenter aware

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

by Federation

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

optimistic locking

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

Can implement custom security layer via applications

Access rights based on private key authentication or shared access signatures

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

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

provided by Google News

How to use Azure Table storage in .Net
10 July 2024, InfoWorld

Working with Azure to Use and Manage Data Lakes
23 July 2024, Simplilearn

Azure Cosmos DB Data Migration tool imports from Azure Table storage
5 May 2015, Microsoft

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Introducing the Amazon Timestream for LiveAnalytics Prometheus Connector
8 July 2024, AWS Blog

How to Monitor an Ubuntu Server With Prometheus: Collecting and Visualizing System Metrics
9 July 2024, Linux Journal

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus
10 March 2024, AWS Blog

Consider Grafana vs. Prometheus for your time-series tools
18 October 2021, TechTarget

My Prometheus is Overwhelmed! Help!
24 July 2021, hackernoon.com

provided by Google News

Share this page