Hi All, I need your advice on below approaches for handling a scenari

Hi All,

I need your advice on below approaches for handling a scenario.

Scenario:- We have something like a Header/Detail tables. Each header record can contain around 100-200 detail records. User input the Header ID ; we need to get all the detail records and process each one of them and does DB update
Approach 1: Can we go for MNI ,for each detail record ; simultaneously processing all detail records.
Approach 2: In a single sub-process get all detail records ; subject each record through some business logic. Once all detail records are subjected to processing , the CDT which holds all these detail records is used for the Detail DB Update. (Single Update ,but containing all records)
Which among the above two approaches is best for handling this scenario w.r.t to performance and stability of platform. fyi, this is not a batch process ,but an interactive process where the header is keyed in by the user.

OriginalPostID-191410

OriginalPostID-191410

  Discussion posts and replies are publicly visible

Parents
  • Thank you Sikhivahans/Nicholas ,your inputs are really valuable.Regarding messaging to even out the load across engines,I am afraid as my understanding is messaging may not work well if I need this processes to be synchronous.Unless and until i update all 200 odd detail records,I cannot proceed further with my process.So not sure whether messaging which otherwise is a best solution suits this situation.I will try with batching as explained by you guys
Reply
  • Thank you Sikhivahans/Nicholas ,your inputs are really valuable.Regarding messaging to even out the load across engines,I am afraid as my understanding is messaging may not work well if I need this processes to be synchronous.Unless and until i update all 200 odd detail records,I cannot proceed further with my process.So not sure whether messaging which otherwise is a best solution suits this situation.I will try with batching as explained by you guys
Children
No Data