#big data nested api call
24 messages · Page 1 of 1 (latest)
You'll need to explain what your use case is in more detail and what you need from us.
What i need is
I have about 4 models
And they are all connected with foreign key
So model 1
We have grandfather
Model 2 father
Model 3 son
Model 4 grandson
I want i way to expose all of them on one vue js page
Is it better to have them nested in one big api call
Or separate
It depends on your ux needs and the size of the data.
Data is too big
First model has less than than second model and so on
Cascade
What is your advice
I don't have enough details to help. My generic advice is to get something up and working first, then iterate.
If the total number of objects is less than 1000, then you could probably do it in one API request. If it's more than 1000, you should break it up. Anywhere in the 100-1000 range, it's hard to say.
No it will exceed 30000
And even more
So breaking it is the way to go
But pardon me
Why 1000 exactly
Experience? I have no justification. It could be 500, it could be 3000.
It's all going to depend on various aspects of your environment, users, and application.
Any recommendation of the best way to view this to clients
I mean from design perspective
of things to click then another things came up and so on
You need to include more details.
How i could visualize a nested data
Try searching for UI examples. Tailwind has some components that may inspire you https://tailwindcomponents.com/components/dashboard
Bootstrap has example pages as well: https://getbootstrap.com/docs/5.2/examples/
Thank you very much
But i have an update
I have my data in hireachy and the bad news is
This is my hireachy in normal
1 -> 2 -> 3 -> 4
But also it could be like this
1 -> 2 -> 4
That means i need to make one big endpoint
Or you have another idea
You can make anything work. That's the nice thing about software.
I don't have a suggestion though.
Yeah it will work on say in that
But efficiency?