Ory Kratos Identity Retrieval: Admin API Pagination vs. External Indexing

When managing a large volume of users in Ory Kratos, retrieving specific subsets of identities requires a choice between utilizing the native Admin API or implementing an external data synchronization layer.

The Admin API provides pagination via page and per_page parameters, which allows for sequential traversal of the identity dataset. However, the API's filtering capabilities are limited to basic traits, and high per_page values can increase memory pressure on the Kratos service.

For complex bounding queries or full-text search, the documented architectural pattern involves syncing identity data to an external database or search engine to avoid overloading the identity server with expensive queries.

• What are the performance thresholds where Admin API pagination becomes inefficient compared to an external index?
• Under what specific trait-filtering constraints does the Admin API fail to provide a performant bounding query?