Why Pagination (from/size) in Elasticsearch? - Purpose & Use Cases

The Big Idea

What if you could instantly jump to any page of millions of results without waiting forever?

The Scenario

Imagine you have a huge list of search results, like thousands of books in a library. You want to show only 10 books per page on your website. Without pagination, you'd have to load all books at once, which is like carrying the entire library every time you want to see just a few books.

The Problem

Loading all results at once is slow and uses a lot of memory. It makes your website lag and frustrates users. Also, manually slicing the results after fetching them wastes time and resources, especially when the list is very large.

The Solution

Pagination with from and size in Elasticsearch lets you ask for just a small chunk of results at a time. You say, "Start from this position and give me this many results." This way, you only get what you need, making your app faster and smoother.

Before vs After

✗ Before

{ "query": { "match_all": {} }, "size": 10 }  # fetches first 10 results by default

✓ After

{ "from": 10, "size": 10, "query": { "match_all": {} } }  # fetches 10 results starting from 11th

What It Enables

It enables fast, efficient browsing through large sets of data by loading only small, manageable pieces at a time.

Real Life Example

When shopping online, you see products page by page. Pagination helps the website show just 20 products per page instead of loading thousands all at once, making your shopping experience quick and easy.

Key Takeaways

Loading all data at once is slow and heavy.

Pagination with from and size fetches only needed results.

This makes apps faster and user-friendly.