DBMS > Heroic vs. NSDb

System Properties Comparison Heroic vs. NSDb

Please select another system to include it in the comparison.

Our visitors often compare Heroic and NSDb with Trino, H2 and Databricks.

Editorial information provided by DB-Engines

Name

Description

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Time Series DBMS

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

Score	0.02
Rank	#364	Overall
	#39	Time Series DBMS

Score	0.00
Rank	#382	Overall
	#41	Time Series DBMS

Website

github.com/spotify/heroic

nsdb.io

Technical documentation

spotify.github.io/heroic

nsdb.io/Architecture

Developer

Spotify

Initial release

2014

2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Java, Scala

Server operating systems

Linux
macOS

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

Supported programming languages

Java
Scala

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

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

Recent citations in the news

How Code Wizards load tested Heroic Labs’ Nakama to two million concurrent players with AWS
1 October 2024, Amazon Web Services

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

provided by Google News

Share this page