DBMS > FatDB vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Sadas Engine vs. Yaacomo

System Properties Comparison FatDB vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Sadas Engine 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

Globally distributed, horizontally scalable, multi-model database service

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Primary database model

Document store
Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

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

azure.microsoft.com/services/cosmos-db

www.sadasengine.com

yaacomo.com

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

FatCloud

Circonus LLC.

Microsoft

SADAS s.r.l.

Q2WEB GmbH

Initial release

2012

2017

2014

2006

2009

Current release

V0.10.20, January 2018

8.0

License

Commercial or Open Source

commercial

free trial version available

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++

C++

Server operating systems

Windows

Linux

hosted

AIX
Linux
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

Via inetgration in SQL Server

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

SQL-like query language

yes

APIs and other access methods

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

HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC
Proprietary protocol

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#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes, in Lua

JavaScript

Triggers

yes

via applications

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

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

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

managed by 'Learn by Usage'

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights can be defined down to the item level

Access rights for users, groups and roles according to SQL-standard

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.