Skip to main content

ESS - 2.Challenges in implementing Search

Perfect Search implementation needs to consider many challenges here's a list of the current day technical challenges:


  1.  A very basic search implementation would be searching the documents by using simple text matching this works fine however such an implementation can be used only when you have really accurate details of what to search any change in the wording, tenses or phrases will give you uncertain results.
  2. Search engines must be capable of constantly learning from users behavior and constantly improving search engine results. For example, on a search query you got a list of results and most of the users are ignoring the top ones and going for 3rd or 4th one you must provide those results first next time.
  3. Map similar queries and provide appropriate search results. Consider a search for "Elasticsearch Getting Started" & "Introduction Elasticsearch" & "Elasticsearch tutorial", the expected results are almost same for each query an efficient engine will determine the parallels, phrasing and any typos to serve similar results every-time.
  4. Continuous Indexing, Indexing is really crucial in search after all it is the concept Search works on. It is the way to organize existing website information in a format for fast retrieval of results for a query. Along with indexing preexisting information, a system had to be put in place to continuously update index with the changes to the data in your website.
  5. Business Focused, You may want to tweak search results based on your business need in some scenarios having such customization's are needed to deliver appropriate results to targeted customers.
  6. Natural Language Processing, Google search queries we perform are a good example to think of without NLP most of our search queries would take a light year to provide relevant results.


Image result for funny google search

So behind a simple click 🔍 there are lot of algorithms and tools working for you to provide most appropriate results. We'll unveil how to use modern search engines to solve most of the challenges by the end of this series.

Happy Learning ✌

Comments

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...

RADUS#4 - Caching the response in REST API's

  Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...

Set BIND VARIABLE and EXECUTE QUERY programmatically in ADF

A very common scenario in ADF is to set a bind variable and execute query programmatically within AMImpl/ VOImpl classes. Here's a simple way to do this: To set bind variable for all rowsets:       ViewObjectImpl someVO = this.getSomeViewObject();       VariableValueManager vMngr = someVO.ensureVariableManager();        vMngr.setVariableValue("DefinedBindVariable",value);        someVO,executeQuery(); To set bind variable for default rowset:          ViewObjectImpl someVO = this.getSomeViewObject();          someVO.setNamedWhereClauseParam("DefinedBindVariable",value);          someVO,executeQuery();