DBMS > Heroic vs. InfinityDB vs. PostGIS vs. Riak KV

System Properties Comparison Heroic vs. InfinityDB vs. PostGIS vs. Riak KV

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

A Java embedded Key-Value Store which extends the Java Map interface

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

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

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

github.com/spotify/heroic

boilerbay.com

postgis.net

Technical documentation

spotify.github.io/heroic

boilerbay.com/infinitydb/manual

postgis.net/documentation

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Spotify

Boiler Bay Inc.

OpenSource, formerly Basho Technologies

Initial release

2014

2002

2005

2009

Current release

4.0

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

All OS with a Java VM

Linux
OS X

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

restricted

SQL

Support of SQL

yes

APIs and other access methods

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

HTTP API
Native Erlang Interface

Supported programming languages

Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

based on PostgreSQL

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

based on PostgreSQL

selectable replication factor

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

links between data sets can be stored

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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.

User concepts

Access control

yes

based on PostgreSQL

yes, using Riak Security

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

provided by Google News

Share this page