DBMS > Apache Impala vs. InfluxDB vs. OpenSearch vs. OrigoDB

System Properties Comparison Apache Impala vs. InfluxDB vs. OpenSearch vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

DBMS for storing time series, events and metrics

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Time Series DBMS

Search engine

Document store
Object oriented DBMS

Secondary database models

Document store

Spatial DBMS

with GEO package

Vector DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

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

Website

impala.apache.org

www.influxdata.com/products/influxdb-overview

github.com/opensearch-project
opensearch.org

origodb.com

Technical documentation

impala.apache.org/impala-docs.html

docs.influxdata.com/influxdb

opensearch.org/docs/latest

origodb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Amazon Web Services

Robert Friberg et al

Initial release

2013

2021

2009

under the name LiveDB

Current release

4.1.0, June 2022

2.7.6, April 2024

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT-License; commercial enterprise version available

Open Source

Apache Version 2.0

Open Source

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++

Java

Server operating systems

Linux

Linux
OS X

through Homebrew

All OS with a Java VM

Linux
Windows

Data scheme

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

Numeric data and Strings

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC

HTTP API
JSON over UDP

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Triggers

yes

by using the 'percolation' feature

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

in enterprise version only

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

in enterprise version only

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

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

In-memory capabilities

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

yes

Depending on used storage engine

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

simple rights management via user accounts

Role based authorization

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

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

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

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

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

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

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

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

News

Converting Timestamp to Date in Java
7 May 2024

A Detailed Guide to C# TimeSpan
2 May 2024

The Final Frontier: Using InfluxDB on the International Space Station
30 April 2024

Getting the Current Time in C#: A Guide
26 April 2024

Sync Data from InfluxDB v2 to v3 With the Quix Template
8 April 2024

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.