DBMS > EsgynDB vs. Heroic vs. Infobright vs. Riak KV

System Properties Comparison EsgynDB vs. Heroic vs. Infobright vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Distributed, fault tolerant key-value store

Primary database model

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

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.esgyn.cn

github.com/spotify/heroic

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

spotify.github.io/heroic

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

Developer

Esgyn

Spotify

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenSource, formerly Basho Technologies

Initial release

2015

2014

2005

2009

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

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

C++, Java

Java

Erlang

Server operating systems

Linux

Linux
Windows

Linux
OS X

Data scheme

yes

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

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

Java Stored Procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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, 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

Recent citations in the news

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

provided by Google News

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

Photos: Woodstock music graduate Alex Riak returns to work with students
11 December 2023, Shaw Local News Network

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

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

provided by Google News

Share this page