DBMS > FatDB vs. Heroic vs. Microsoft Azure SQL Database vs. Riak TS

System Properties Comparison FatDB vs. Heroic vs. Microsoft Azure SQL Database vs. Riak TS

Please select another system to include it in the comparison.

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.

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Database as a Service offering with high compatibility to Microsoft SQL Server

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

github.com/spotify/heroic

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

spotify.github.io/heroic

docs.microsoft.com/en-us/azure/azure-sql

www.tiot.jp/riak-docs/riak/ts/latest

Developer

FatCloud

Spotify

Microsoft

Open Source, formerly Basho Technologies

Initial release

2012

2014

2010

2015

Current release

V12

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

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

Java

C++

Erlang

Server operating systems

Windows

hosted

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

via Elasticsearch

yes

restricted

SQL

Support of SQL

Via inetgration in SQL Server

yes

yes, limited

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

via applications

Transact SQL

Erlang

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

yes, with always 3 replicas available

selectable replication factor

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

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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.

User concepts

Access control

Can implement custom security layer via applications

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

DB-Engines blog posts

PostgreSQL is the DBMS of the Year 2020
4 January 2021, Paul Andlinger, Matthias Gelbmann

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

The popularity of cloud-based DBMSs has increased tenfold in four years
7 February 2017, Matthias Gelbmann

show all

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Copilot in Azure SQL Database in Private Preview
27 March 2024, InfoQ.com

Microsoft unveils Copilot for Azure SQL Database
27 March 2024, InfoWorld

Azure SQL Database migration to OCI - resources estimation and migration approach
11 January 2024, Oracle

Public Preview: New Azure SQL Database skills introduced to Microsoft Copilot in Azure | Azure updates
21 May 2024, azure.microsoft.com

Azure SQL Database takes Saturday off on US east coast following network power failure
18 September 2023, The Register

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

provided by Google News

Share this page