DBMS > FatDB vs. Heroic vs. Splunk vs. TempoIQ

System Properties Comparison FatDB vs. Heroic vs. Splunk vs. TempoIQ

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.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines 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

Analytics Platform for Big Data

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Key-value store

Time Series DBMS

Search engine

Time Series DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

github.com/spotify/heroic

www.splunk.com

tempoiq.com (offline)

Technical documentation

spotify.github.io/heroic

docs.splunk.com/Documentation/Splunk

Developer

FatCloud

Spotify

Splunk Inc.

TempoIQ

Initial release

2012

2014

2003

2012

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition 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

Java

Server operating systems

Windows

Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

Via inetgration in SQL Server

Splunk Search Processing Language for search commands

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

HTTP REST

HTTP API

Supported programming languages

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Realtime Alerts

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

Multi-source 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

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

Access rights for users and roles

simple authentication-based access control

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

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger