DBMS > Ignite vs. Infobright vs. OrigoDB vs. SAP HANA

System Properties Comparison Ignite vs. Infobright vs. OrigoDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

A fully ACID in-memory object graph database

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

Primary database model

Key-value store
Relational DBMS

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

ignite.apache.org

ignitetech.com/softwarelibrary/infobrightdb

origodb.com

www.sap.com/products/hana.html

Technical documentation

apacheignite.readme.io/docs

origodb.com/docs

help.sap.com/hana

Developer

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

Robert Friberg et al

SAP

Initial release

2015

2005

2009

under the name LiveDB

2010

Current release

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

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

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

C++, Java, .Net

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

Appliance or cloud-service

Data scheme

yes

Typing

predefined data types such as float or date

yes

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.

yes

can be achieved using .NET

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

SQLScript, R

Triggers

yes (cache interceptors and events)

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.