Node-Based UIs in React – React Flow
is anyone familiar with ReactFlow (https://reactflow.dev/) ?
I have a doubt on how to structure the Convex DB schema to save the flows. More precisely, I don't know if it is better/more performant to store everything (nodes and edges) in a single document under an hypothetical
flows table or store each node as a single document under another table.
I feel like with the first option, the data associated with each node could result in a giant documentNode-Based UIs in React – React Flow
Highly customizable React library for workflow builders, no-code apps, image processing, visualizers, and more
3 Replies
I'm not familiar with ReactFlow, but for databases in general, not just Convex, your query will return all the data of the entire row/document
welll I know that I was just questioning which strategy for the schema was better
I don't think there's a generally useful answer to this question. Only you know all the numbers involved. You could post all the numbers to this Discord, but then it'd be public
The fact that there is even the possibility to store everything in a single doc makes me lean toward trying that until you run into problems
But I think saying what the columns would be would help clarify the matter