DBMS > Infobright vs. Oracle NoSQL vs. OrigoDB vs. SAP HANA

System Properties Comparison Infobright vs. Oracle NoSQL vs. OrigoDB 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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A fully ACID in-memory object graph database

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

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Document store
Object oriented DBMS

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	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.oracle.com/database/nosql/technologies/nosql

origodb.com

www.sap.com/products/hana.html

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

origodb.com/docs

help.sap.com/hana

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

Robert Friberg et al

SAP

Initial release

2005

2011

2009

under the name LiveDB

2010

Current release

24.1, May 2024

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

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

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

Server operating systems

Linux
Windows

Linux
Solaris SPARC/x86

Linux
Windows

Appliance or cloud-service

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles

Role based authorization

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.