---
title: "Elasticsearch"
description: "Elasticsearch is a distributed full-text search and analytics engine built on Lucene. Learn about indexes, cluster architecture and common use cases."
url: "https://nodea.io/en/glossary/elasticsearch"
lang: "en"
updated: "2026-07-13"
---

# Elasticsearch

> Elasticsearch is a distributed full-text search and analytics engine built on the Apache Lucene library, enabling near-instant search across massive datasets.

**Elasticsearch** is a distributed full-text search and analytics engine built on the Apache Lucene library and exposed through a simple JSON-based API. Its job is to search enormous datasets — text, logs, metrics — in a fraction of a second, taking relevance, typos and word variants into account. Together with Logstash and [Kibana](https://nodea.io/en/glossary/kibana) it forms the popular analytics toolkit known as the ELK stack.

## How Elasticsearch works

At its heart lies an **inverted index**: instead of scanning documents to find a word, Elasticsearch maintains a map that, for each term, points to every document containing it. This makes searching across millions of records almost instantaneous. The key concepts are:

- **Document** — a single record in JSON format, the basic unit of data.
- **Index** — a logical collection of similarly structured documents, the equivalent of a table.
- **Shard** — an index is split into shards spread across many nodes, enabling horizontal scaling.
- **Replica** — a copy of a shard that boosts availability and read performance.

Elasticsearch runs as a cluster of many nodes that automatically distribute data and take over each other's work if one fails, making it resilient and easy to scale. It is a [NoSQL](https://nodea.io/en/glossary/nosql) store, holding data without a rigid relational schema.

## Elasticsearch in practice

The most common use cases are product search in e-commerce stores, searching content across portals and — above all — centralised collection and analysis of [server logs](https://nodea.io/en/glossary/server-logs) and application metrics in [big data](https://nodea.io/en/glossary/big-data) environments. DevOps teams rely on it to monitor and quickly diagnose issues in distributed systems, visualising the gathered data on Kibana dashboards.

### How does Elasticsearch differ from a traditional SQL database?

A relational SQL database is optimised for transactions and precise key lookups but is slow at full-text search across millions of rows. Elasticsearch is the opposite: it builds an inverted index of words, returning relevant text results in milliseconds and offering relevance scoring and language analysis, though it does not replace a transactional database.

## Related

- [Kibana](https://nodea.io/en/glossary/kibana)
- [Server logs](https://nodea.io/en/glossary/server-logs)
- [MongoDB](https://nodea.io/en/glossary/mongodb)
- [NoSQL](https://nodea.io/en/glossary/nosql)
- [Big data](https://nodea.io/en/glossary/big-data)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/elasticsearch.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)