DBMS > Cachelot.io vs. Heroic vs. SAP HANA vs. SiteWhere

System Properties Comparison Cachelot.io vs. Heroic vs. SAP HANA vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

In-memory, column based data store. Available as appliance or cloud service

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

cachelot.io

github.com/spotify/heroic

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

Technical documentation

spotify.github.io/heroic

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

Developer

Spotify

SAP

SiteWhere

Initial release

2015

2014

2010

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

FreeBSD
Linux
OS X

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

Memcached protocol

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

JDBC
ODBC

HTTP REST

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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.

yes

User concepts

Access control

yes

Users with fine-grained authorization concept

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.