DBMS > Heroic vs. Infobright vs. SAP HANA vs. SWC-DB

System Properties Comparison Heroic vs. Infobright vs. SAP HANA vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

A high performance, scalable Wide Column DBMS

Primary database model

Time Series DBMS

Relational DBMS

Wide column store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/spotify/heroic

ignitetech.com/softwarelibrary/infobrightdb

www.sap.com/products/hana.html

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

spotify.github.io/heroic

help.sap.com/hana

Developer

Spotify

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP

Alex Kashirin

Initial release

2014

2005

2010

2020

Current release

2.0 SPS07 (April 4, 2023), April 2023

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

GPL V3

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

Java

C++

Server operating systems

Linux
Windows

Appliance or cloud-service

Linux

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.

Secondary indexes

yes

via Elasticsearch

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.