Why Elasticsearch exists - The Real Reasons

The Big Idea

What if you could find any piece of information instantly, no matter how much data you have?

The Scenario

Imagine you have thousands or millions of documents, like emails, articles, or product listings, stored in simple files or basic databases. You want to find specific information quickly, like all emails mentioning "meeting" from last month or products under $50 with good reviews.

The Problem

Searching through all those files or basic databases one by one is painfully slow and frustrating. You might write complex code to scan every document, which takes a lot of time and often misses relevant results or returns too many unrelated ones.

The Solution

Elasticsearch solves this by organizing data in a smart way that makes searching lightning fast and accurate. It creates indexes that work like an advanced library catalog, letting you find exactly what you want instantly, even in huge amounts of data.

Before vs After

✗ Before

for doc in documents:
    if 'meeting' in doc.text:
        print(doc)

✓ After

GET /emails/_search
{
  "query": {
    "match": { "text": "meeting" }
  }
}

What It Enables

It enables instant, powerful search and analysis on massive data sets, making information easy to find and use.

Real Life Example

Online stores use Elasticsearch to let customers quickly find products by name, category, price, and reviews, even when they have millions of items.

Key Takeaways

Manual searching through large data is slow and error-prone.

Elasticsearch indexes data for fast, accurate search.

This makes handling huge amounts of information easy and efficient.

Practice

1. Why was Elasticsearch created?
Elasticsearch is mainly used because:

easy

A. It helps find and analyze large amounts of data quickly

B. It is a programming language for building websites

C. It stores data only in spreadsheets

D. It is used to design graphics and images

Solution

1. Step 1: Understand Elasticsearch's purpose

   Elasticsearch is designed to search and analyze data fast, especially large or complex data.

2. Step 2: Compare options with Elasticsearch's use

   The options claiming it is a programming language, stores data only in spreadsheets, or is used for graphics are incorrect.

3. Final Answer:

   It helps find and analyze large amounts of data quickly -> Option A

4. Quick Check:

   Elasticsearch = Fast data search and analysis [OK]

Hint: Elasticsearch = fast search and analysis tool [OK]

Common Mistakes:

• Thinking Elasticsearch is a programming language
• Confusing it with spreadsheet software
• Assuming it is for graphic design

2. Which of the following is the correct way to send a search query to Elasticsearch?

easy

A. Writing SQL queries directly in Elasticsearch console

B. Using JSON format over HTTP

C. Using XML files uploaded manually

D. Sending plain text emails to Elasticsearch server

Solution

1. Step 1: Identify Elasticsearch query method

   Elasticsearch uses JSON queries sent over HTTP to interact with data.

2. Step 2: Eliminate incorrect methods

   SQL, XML uploads, and emails are not how Elasticsearch receives queries.

3. Final Answer:

   Using JSON format over HTTP -> Option B

4. Quick Check:

   Elasticsearch queries = JSON + HTTP [OK]

Hint: Elasticsearch queries use JSON over HTTP [OK]

Common Mistakes:

• Assuming Elasticsearch uses SQL queries
• Thinking XML files are used for queries
• Believing email can send queries

3. What will Elasticsearch do when you send this JSON query?

{"query": {"match": {"title": "coffee"}}}

medium

A. Return an error because the query is invalid

B. Delete all documents with the title 'coffee'

C. Update the title field to 'coffee' in all documents

D. Search documents where the title contains the word 'coffee'

Solution

1. Step 1: Understand the JSON query structure

   The query uses "match" on the "title" field with the word "coffee" to find matching documents.

2. Step 2: Identify the query action

   This is a search query, not a delete or update command, so it returns matching documents.

3. Final Answer:

   Search documents where the title contains the word 'coffee' -> Option D

4. Quick Check:

   Match query = search for matching text [OK]

Hint: Match query finds documents containing the word [OK]

Common Mistakes:

• Confusing search with delete or update
• Thinking the query syntax is invalid
• Assuming it changes data instead of searching

4. You wrote this query to find documents with 'apple' in the description:

{"query": {"match": {"description": "apple"}}

But Elasticsearch returns an error. What is wrong?

medium

A. The field name 'description' is invalid

B. The word 'apple' is not allowed in queries

C. The JSON query is missing a closing brace '}'

D. Elasticsearch does not support match queries

Solution

1. Step 1: Check JSON syntax carefully

   The query is missing a closing brace '}' at the end, making it invalid JSON.

2. Step 2: Verify other options

   Words like 'apple' are allowed, 'description' can be a valid field, and match queries are supported.

3. Final Answer:

   The JSON query is missing a closing brace '}' -> Option C

4. Quick Check:

   JSON syntax error = missing brace [OK]

Hint: Always check JSON braces and commas carefully [OK]

Common Mistakes:

• Ignoring JSON syntax errors
• Assuming certain words are banned
• Thinking field names must be predefined

5. You have a large dataset with millions of records and want to quickly find all entries mentioning 'travel' in any text field. Why is Elasticsearch a good choice for this?

hard

A. Because it indexes data for fast full-text search across many fields

B. Because it stores data only in small files for quick access

C. Because it uses SQL joins to combine travel data efficiently

D. Because it compresses data to save disk space only

Solution

1. Step 1: Understand Elasticsearch's indexing

   Elasticsearch creates indexes that allow very fast full-text search across large datasets and multiple fields.

2. Step 2: Evaluate other options

   It does not rely on small files only, SQL joins, or just compression for speed.

3. Final Answer:

   Because it indexes data for fast full-text search across many fields -> Option A

4. Quick Check:

   Indexing = fast search on big data [OK]

Hint: Indexing enables fast search on large data [OK]

Common Mistakes:

• Thinking Elasticsearch uses SQL joins
• Believing it only compresses data
• Assuming it stores data in small files only