Hi guys! Congrats for what you have built. I have one question for now. Within our travel app (and database) we have different types (and tables) of elements, such as Attractions, Destinations, Countries, Users. What’s the best way to structure the index so we can be able to display something like this on the front-end? For example when someone is searching for “Paris”: we expect to have a top result (which can be any type, just getting the 1st search result), then all the results separately based on the element type. Thanks!

Thanks Robert! The UI was very helpful context. I'd recommend storing each of Attractions, Destinations, Countries, Users, etc in separate collections and then do a multi-search to get results from multiple collections. Then to show the top result, one thing you could do is: assuming you have some sort of metric in each record across different types to indicate popularity (for eg number of reviews, etc), you could pick the first result from each of the individual collections' results, see which one has the max popularity score and display that

Thanks @Jason Bosco. Will start testing early next week and will come back with updates on this.