DBMS > EXASOL vs. Firebase Realtime Database vs. IRONdb vs. OpenSearch

System Properties Comparison EXASOL vs. Firebase Realtime Database vs. IRONdb vs. OpenSearch

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Primary database model

Secondary database models

Vector DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

www.exasol.com

firebase.google.com/products/realtime-database

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

github.com/opensearch-project
opensearch.org

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/database

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

opensearch.org/docs/latest

Developer

Exasol

Google

acquired by Google 2014

Circonus LLC.

Amazon Web Services

Initial release

2000

2012

2017

2021

Current release

V0.10.20, January 2018

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

hosted

Linux

All OS with a Java VM

Data scheme

yes

schema-free

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

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

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

SQL-like query language

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

Java
Lua
Python
R

Java
JavaScript
Objective-C

.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

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

yes, in Lua

yes

Triggers

yes

Callbacks are triggered when data changes

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

Transaction concepts

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

ACID

yes

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

Access rights for users, groups and roles according to SQL-standard

yes, based on authentication and database rules

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.