Why documents are the unit of data in Elasticsearch - Visual Breakdown

Concept Flow - Why documents are the unit of data

User sends data

↓

Data split into documents

↓

Each document indexed separately

↓

Documents stored in shards

↓

Search queries run on documents

↓

Results returned based on document matches

Data is broken into documents, each stored and searched independently, making Elasticsearch fast and flexible.

Execution Sample

Elasticsearch

POST /library/_doc/1
{
  "title": "Learn Elasticsearch",
  "author": "Jane"
}

This adds a single document with book info to the 'library' index.

Execution Table

Step	Action	Data Unit	Storage Location	Effect
1	Receive data from user	Raw JSON	N/A	Data ready to be processed
2	Split data into documents	Single document	N/A	Each document is a self-contained unit
3	Index document	Document	Shard in index	Document stored and searchable
4	Run search query	Documents	Shards	Matches found per document
5	Return results	Documents	N/A	User gets relevant documents

💡 All data is handled as documents, enabling efficient storage and search.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
data	Raw JSON input	Split into documents	Indexed documents	Queried documents	Search results

Key Moments - 2 Insights

Why does Elasticsearch treat data as documents instead of rows or columns?

Because each document is a complete, self-contained unit of data that can be indexed and searched independently, as shown in execution_table step 3.

How does storing data as documents improve search speed?

Documents are stored in shards and indexed separately, allowing Elasticsearch to quickly find matches without scanning entire datasets, as seen in execution_table steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the data split into documents?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Check the 'Action' column for 'Split data into documents' in execution_table.

According to variable_tracker, what is the state of 'data' after Step 3?

A Raw JSON input

B Indexed documents

C Split into documents

D Search results

💡 Hint

Look at the 'After Step 3' column for 'data' in variable_tracker.

If Elasticsearch did not use documents as units, what would likely happen to search speed?

A Search speed would slow down

B Search speed would improve

C Search speed would stay the same

D Search speed would be unpredictable

💡 Hint

Refer to key_moments about why documents improve search speed.

Concept Snapshot

In Elasticsearch, data is stored as documents.
Each document is a self-contained JSON object.
Documents are indexed separately for fast search.
This design allows flexible, scalable data handling.
Search queries match documents, not rows or columns.

Full Transcript

Elasticsearch treats data as documents because each document is a complete unit of information. When data is received, it is split into these documents. Each document is then indexed and stored in shards within the Elasticsearch cluster. This allows Elasticsearch to quickly search and retrieve relevant documents when a query is run. Handling data as documents rather than rows or columns improves speed and flexibility. The execution table shows the steps from receiving data to returning search results, and the variable tracker follows the state of data through these steps. Key moments clarify why documents are used and how they help search performance. The visual quiz tests understanding of these steps and concepts.