Restaurants sorting according to their rates is not scalable #27
Description
Context
In ViewSearchResult component, The frontend gets the the whole search result of the user's query and sort them according to their rates in the browser.
Problem
This approach is not scalable at all, things can get unpleasant when the search result is large. With large results, the payload of the data transferred will be huge and the sorting algorithms will stall the result more from being viewed to the user.
Idea
I think we should move the sorting of the search result to the backend and chop the results into segments and send them as the user proceed into the search result. This will not be a very fast approach but it will prevent overwhelming the user with a very large dataset.