NEW
A distributed, RESTful search and analytics engine built on Lucene for full-text, structured, and observability use cases.
DESCRIPTION
Elasticsearch indexes documents into inverted indices for fast search and aggregations. It scales horizontally with shards and replicas, exposing a REST API and Query DSL. Common uses include application search, log analytics (ELK), metrics, and security analytics. It integrates with Beats, Logstash, and Kibana for ingestion and visualization. Proper index lifecycle management, shard sizing, and mappings are critical for performance and cost.
ALTERNATIVE DEFINITIONS
Elastic
Elasticsearch is a distributed, RESTful search and analytics engine for all types of data.
Stresses multi-data-type support and distributed, RESTful architecture.
Elastic
Elasticsearch is built on Apache Lucene and provides a distributed, multitenant-capable full-text search engine with an HTTP web interface.
Notes Lucene foundation and operational characteristics like multitenancy.
RELATED TERMS
Lucene Inverted Index Kibana Full-Text Search Query DSL Shards Replicas Elasticsearch Cluster Elasticsearch Ingest
COMPETING TERMS
KNOWLEDGE AREAS
Data Storage & Operations Data Engineering Observability & Telemetry
TARGET AUDIENCE
Software Developer Data Engineer DevOps Engineer
EXTERNAL SOURCES
- Wikipedia - Elasticsearch
- Elastic - Official Elasticsearch documentation
- Elastic - Index lifecycle management
- Apache Logging - Logstash ingestion framework
TOP QUESTIONS
What problems does Elasticsearch solve well?
It excels at full-text search, log analytics, time-series aggregations, and powering search experiences with low-latency queries.
Category: UseCases
How does Elasticsearch scale?
It shards indices across nodes and replicates for resilience. Proper shard counts and index lifecycle management are key.
Category: Scalability
What’s the difference between Elasticsearch and OpenSearch?
OpenSearch is a community-driven fork. Feature sets diverge; licensing and ecosystem preferences often drive choice.
Category: Comparison
How do mappings affect Elasticsearch performance?
Mappings define field types and analyzers. Correct mappings prevent expensive queries and reduce storage overhead.
Category: BestPractices
What are common Elasticsearch pitfalls?
Oversharding, dynamic mapping explosions, and unbounded index growth cause instability and high costs.
Category: Mistakes
How is security implemented in Elasticsearch?
Use TLS, role-based access controls, API keys, and network isolation. Managed services simplify security defaults.
Category: Security
How should I size Elasticsearch clusters?
Estimate shard counts, index rates, and query patterns, then benchmark. Use hot-warm-cold tiers for cost control.
Category: Requirements
When should I choose Elasticsearch over a relational database?
Choose Elasticsearch for flexible search, relevance ranking, and aggregations over documents; use RDBMS for strong relational consistency.
Category: Opinion
What is the ELK stack in relation to Elasticsearch?
ELK stands for Elasticsearch, Logstash, and Kibana, often used together for log analytics pipelines and dashboards.
Category: Overview