Magento 2.3: Difference b/w Elastic search and Built-In search

All we need is an easy explanation of the problem, so here it is.

I’ve searched about difference between Elastic search and Built-In search option available in the Magento search configuration but didn’t find an answer regarding the same.

I want to know the difference between these two options.

Thanks in advance for your better support.

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

We have worked with the Search and from my point of view:

Built In Search:

  1. This is MYSQL Search
  2. Here Data loads from Database that’s why it is time consuming process.
  3. It effects on site performance.

Elastic Search:

  1. Basically it works with proxy server.

  2. Here search request sends to proxy server and return response in the
    form of Json.

  3. Site Performance Improves.

Note: Elastic search,which natively supports Lucene (a-search-engine-library ) can help you search existing data with the help of its REST_API or Query String.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply