• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 10271 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Process

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

georgej
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
  • 0
    @georgej I would like to suggest to follow the asynchronous approach by keeping the memory intensive operations we are performing. So, from my perspective, it's better to educate the user saying that activity chaining can't be offered and run the process asynchronously thereby giving the process enough time to complete, and in parallel we can have a good design in place.

    Further I would like to add one more input - See what database can effectively do for you in this entire use-case. For instance, few operations can be effectively implemented in database when compared to Appian because of the power and flexibility it has got. The documentation at https://forum.appian.com/suite/help/16.1/Database_Performance_Best_Practices.html might give you an idea.
Reply
  • 0
    @georgej I would like to suggest to follow the asynchronous approach by keeping the memory intensive operations we are performing. So, from my perspective, it's better to educate the user saying that activity chaining can't be offered and run the process asynchronously thereby giving the process enough time to complete, and in parallel we can have a good design in place.

    Further I would like to add one more input - See what database can effectively do for you in this entire use-case. For instance, few operations can be effectively implemented in database when compared to Appian because of the power and flexibility it has got. The documentation at https://forum.appian.com/suite/help/16.1/Database_Performance_Best_Practices.html might give you an idea.
Children
No Data

© 2024 Appian. All rights reserved.