I have a question around searching metadata for our member’s documents. One of our engineers recalls an expert suggesting that once we fully populate Box with our approx. 9 TBs of documents (~200M) and their associated metadata, we would not be able to search using the Box Metadata API endpoint for a unique member id (internal identifier) on a custom metadata (memberId) tag, to get back a collection of Box document IDs that relate to that particular member.
Instead, he suggested we build and utilize an external SQL database to host member metadata related to Box Folder and Document IDs. Is there any reason why we cannot utilize the Box APIs to do such searches in a performant way instead of having to build an external metadata management system to track this. We are already aware of the search limitation and the need for indices.
Please provide us with some clarification on the best way to handle this, what are the true limitations if any, and how can we overcome them?