DBMS > AlaSQL vs. Heroic vs. IRONdb vs. SAP HANA

System Properties Comparison AlaSQL vs. Heroic vs. IRONdb vs. SAP HANA

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.

Description

JavaScript DBMS library

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

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

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

Primary database model

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

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.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

alasql.org

github.com/spotify/heroic

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

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

spotify.github.io/heroic

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

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

Spotify

Circonus LLC.

SAP

Initial release

2014

2017

2010

Current release

V0.10.20, January 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

commercial

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

JavaScript

Java

C and C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Appliance or cloud-service

Data scheme

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

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

yes

APIs and other access methods

JavaScript API

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

HTTP API

JDBC
ODBC

Supported programming languages

JavaScript

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes, in Lua

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic, metric affinity per node

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

configurable replication factor, datacenter aware

yes

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

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.