I have one API ( voice , mvb, accessories products ) I want to fetch the all the product details form api to aem & storage the product details in node level (Json format ) and creating product components process steps
A few comments have been already made, but I want to give you my view on it.
In short: if it's possible avoid it. Because you will end up with topics like:
how do I structure that data in the repository, so it's not getting slow (too many siblings), and that you don't need search for all operations on it.
Witih your approach you are creating a cache. On product changes how long does it take to propagate changes from the backend to your AEM? Next consider that from end-to-end (changes in the PIM until a enduser can see the changed data), and calculate both the minimum and maximum delay. Is that acceptable?
What about deleting entries from this cache?
In many cases it might be best if you either bypass AEM when you need to display product information (and let the frontend reach out to the PIM directly). You can look at the current Commerce Integration Framework (CIF2) of Adobe; of course this is for a shopping solution, but also for a shop displaying products is a big topic.
Hope to give you some inspiration what to look for.