DBMS > IRONdb vs. Snowflake vs. Sqrrl vs. Yaacomo

System Properties Comparison IRONdb vs. Snowflake vs. Sqrrl vs. Yaacomo

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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

Description

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

Cloud-based data warehousing service for structured and semi-structured data

Adaptable, secure NoSQL built on Apache Accumulo

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

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

www.snowflake.com

sqrrl.com

yaacomo.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

Developer

Circonus LLC.

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Q2WEB GmbH

Initial release

2017

2014

2012

2009

Current release

V0.10.20, January 2018

License

Commercial or Open Source

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

Java

Server operating systems

Linux

hosted

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

APIs and other access methods

HTTP API

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

yes

Sharding

making use of Hadoop

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

selectable replication factor

making use of Hadoop

Source-replica 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

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.