DBMS > IRONdb vs. OpenSearch vs. OrigoDB vs. Sphinx

System Properties Comparison IRONdb vs. OpenSearch vs. OrigoDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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 search engine for searching in data from different sources, e.g. relational databases

Primary database model

Time Series DBMS

Search engine

Document store
Object oriented DBMS

Search engine

Secondary database models

Vector DBMS

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

Score	16.36
Rank	#37	Overall
	#4	Search engines

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.circonus.com/solutions/time-series-database/

github.com/opensearch-project
opensearch.org

origodb.com

sphinxsearch.com

Technical documentation

docs.circonus.com/irondb/category/getting-started

opensearch.org/docs/latest

origodb.com/docs

sphinxsearch.com/docs

Developer

Circonus LLC.

Amazon Web Services

Robert Friberg et al

Sphinx Technologies Inc.

Initial release

2017

2021

2009

under the name LiveDB

2001

Current release

V0.10.20, January 2018

2.5.0, January 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2, commercial licence 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

C and C++

Java

C++

Server operating systems

Linux

All OS with a Java VM

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

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

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

Proprietary protocol

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes

by using the 'percolation' feature

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

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

Foreign keys

Referential integrity

depending on model

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

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

Role based authorization

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.