DBMS > Infobright vs. Newts vs. Riak KV vs. SAP HANA

System Properties Comparison Infobright vs. Newts vs. Riak KV vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS based on Cassandra

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

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.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

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

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

opennms.github.io/newts

www.sap.com/products/hana.html

Technical documentation

github.com/OpenNMS/newts/wiki

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

help.sap.com/hana

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenNMS Group

OpenSource, formerly Basho Technologies

SAP

Initial release

2005

2014

2009

2010

Current release

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

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

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Java

Erlang

Server operating systems

Linux
Windows

Linux
OS X
Windows

Linux
OS X

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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

Knowledge Grid Technology used instead

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP REST
Java API

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

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

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

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

selectable replication factor

yes

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

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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, using Riak Security

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.