Best way to handle large recursive configs in Convex?
❔Advice
We are migrating a complex, deeply nested 3D configuration system to Convex. Our previous client-side approach required loading and processing 4,000–5,000 nodes per configuration, which caused performance issues. We want to move all configuration logic to the backend and fetch only the active parts of a configuration, ideally with pagination.
The main challenge is how to model and query a recursive hierarchy efficiently in Convex. Specifically, we are unsure whether splitting the data into multiple tables such as folders, variantSets, and variants is the right approach, and whether Convex can handle this structure with good performance.
The main challenge is how to model and query a recursive hierarchy efficiently in Convex. Specifically, we are unsure whether splitting the data into multiple tables such as folders, variantSets, and variants is the right approach, and whether Convex can handle this structure with good performance.
