Sitecore Content Hub Bulk Read SDK vs. GraphQL: Performance and Use Cases
Sooner or later every Sitecore Content Hub project gets a request like this: "Can you give us a spreadsheet of every usage right, with its status and expiry dates?" or "Find all assets whose rights expired more than six months ago." In other words, you have to read every entity of one definition . That can be tens of thousands of records, and you need them reliably, without duplicates or gaps. I recently built exactly this for the M.DRM.RightsProfile definition, which holds usage rights. There are two very different APIs for it, and the SDK itself offers two ways to page: The Content Hub Web SDK ( Stylelabs.M.Sdk.WebClient ), using either SearchAfterQuery or the Entity Scroller . Sitecore Experience Edge GraphQL , which can return up to 1,000 records per call . I put both behind a single switch in the same helper, so they write an identical CSV and I could time them against each other. This post covers how each approach works, the traps I hit...