Skip to main content

ESS - 1.Purpose of search and example use cases

Why Search?


Imagine to locate a file in your machine with no search provided in explorer or by the operating system. Sure it's a scary thing to attempt unless you're retired or bored of life :), search saves a ton of time and efforts in these hard-times.

Enterprise Search:

 As we know searching within a single machine for a document itself is tiresome and an enterprise is amassed with many such systems and finding a file in such distributed environments gets really tough. Enterprise search does the lookup for you across all these systems and provides the most relevant results.
Image result for enterprise search
source: programming-free.com

Amazon sold a little over 3 billion products in October 2017, that's a minimum of billion queries unless they found stuff on the home page which is not customized for the consumer suppose if this shopping giant had no search and probably organised stuff by categories and asked you to find your product then your approximate worst case time complexity in finding a product would be somewhere around O(410,058,418) and this only for top 10. Here are the top 10 categories and their distribution:

Top selling products in Amazon
source: scrapehero

So enterprises when they get huge demands the need of a search tool. My bad i forgot the classic Google example if there's no google help imagine finding a document on world wide web.

Search in Analytics:
Having search on website really helps study the customers, business and to plan for the future. when a search is made any analytics on the query will help improve the results over time, know customers requirements, provide suggestions for different products and improve business.

Also the trend of micro-services is huge in which application logs are directly to proportional to the number of services, nodes and their maintenance. Every level introduced requires many levels of logs written to different places, to process all these TB's if not PB's of data and get value out of it search is mandatory.

Here's a sample of metrics from ILS at the time of writing this blog post:



and facebook states that it makes around 60+ million queries per day.

So to conclude the value implementing a search to the business is enormous and it provides better if not best user experience for your consumers, teams e.t.c..

That's it for now on why we need search I'll be discussing on some basic search concepts in my next post.

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 ...

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...