We are prototyping the type sense for global searc...
# community-help
s
We are prototyping the type sense for global search for the internal product which was using SQL server. We have search across 4 different domain entities like device, user application and content . We have a single text box when entered we are searching across all the tables to get the details . Now we are planning to redesign it using typesense. What is the best way to design the document structure. Is de normalise better or have multiple documents and do multi search
j
If you need to visually show your users that these results are from Entity X and these other results are from another Entity Y, then you want to put them in separate collections and do a multi-search.
s
Will that having a scaling issue in terms of response time?
Since Instead of search on one index I might search on 4 now
j
Sending multiple searches in a single search multi_search request has less overhead, and fanning out searches across multiple collections is actually more performant
But I would recommend benchmarking with your particular dataset to asses how it works for you