Box API - Metadata Endpoint Performance
AnsweredWe have a question around searching metadata for a member's documents. One of our engineers recalls a Box consultant telling us that once we fully populate Box with our approx. 9 TBs of documents (~200M) and 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, we were asked to build and utilize an external SQL database to host member metadata related to Box Folder and Document IDs. However, all Box documentation that we’ve read leads us to believe that we can utilize the Box APIs to do such searches in a performant way. No where is there any mention to build an external metadata management system to track this.
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?
-
Hi Abraham,
Welcome to Box Community and glad to help!
Great news! We've opened a new Box Developer Community where you could post all your API inquiries with guaranteed seamless support from our team.
We'd love to have you there!
Please sign in to leave a comment.
Comments
1 comment