DBMS > Infobright vs. OpenSearch vs. OrigoDB vs. RavenDB

System Properties Comparison Infobright vs. OpenSearch vs. OrigoDB vs. RavenDB

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 distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A fully ACID in-memory object graph database

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Search engine

Document store
Object oriented DBMS

Document store

Secondary database models

Vector DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

ignitetech.com/softwarelibrary/infobrightdb

github.com/opensearch-project
opensearch.org

origodb.com

ravendb.net

Technical documentation

opensearch.org/docs/latest

origodb.com/docs

ravendb.net/docs

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Amazon Web Services

Robert Friberg et al

Hibernating Rhinos

Initial release

2005

2021

2009

under the name LiveDB

2010

Current release

2.5.0, January 2023

5.4, July 2022

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 Version 2.0

Open Source

AGPL version 3, commercial license available

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

Server operating systems

Linux
Windows

All OS with a Java VM

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

Multi-source replication

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

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Role based authorization

Authorization levels configured per client per database

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.