Badges on search results about planner HOT 4 CLOSED

This is going to be a little tricky for few reasons

1. Trends update every 30 minutes or so
2. Search result is generated purely from the search index and search service which deliberately does not talk to hadith service or analytics service to speed up the search process, so we have no way of knowing whether hadith is trending or not.

For above reasons, we would most likely need to add a separate Elasticsearch index update job for this (not a good idea though).

from planner.

I think a better solution would be to add another job who's sole purpose would be to update the ahādīth records that are now trending and that are no longer trending
That way the Elasticsearch builder would pick up these records, and update their associated index.

Doing this would also mean we can continue to use search service as it is and pick up the record right from the ES

The downside is cache invalidation but there is also a workaround for that which is search versioning. This would be a little cumbersome especially because our trends change every 30 minute.

from planner.

Another possible (and simpler) solution is asynchronously fetch the badges post search - there is going to be a slight user experience concern here.

from planner.

So we have 3 possible solution to achieve this:

1. New job that would find trends and update the search index (worst option)
2. New job to update the records with new trend and remove old trends and so existing ES job can pick up these records and update the index
   • +simple solution that works with existing eco-system
   • -ddl change for hadith
   • -frequent hadith records update
   • -cache invalidation
3. Asynchronously fetch the badges from hadith service.
   • +simple solution
   • -bad user experience
   • >going to need new GET API

from planner.