Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Suggested Answer
+1
person also asked this
people also asked this
Replies
15 replies
Answers
1 answer
Subscribers
8 subscribers
Views
10994 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi All, I need your advice on below approaches for handling a scenari
georgej
over 8 years ago
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
Nicholas Wurster
over 8 years ago
Agree with @sikhivahans, if you can make this use "messaging" and give the process enough time to distribute the requests this will prevent any negative performance/memory penalties in trying to push all at once. Here is a link for your convenience:
forum.appian.com/.../Messaging_Best_Practices.html
Pay special attention to "passing data by reference" to the sub-process and ensuring the payload itself is small.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Nicholas Wurster
over 8 years ago
Agree with @sikhivahans, if you can make this use "messaging" and give the process enough time to distribute the requests this will prevent any negative performance/memory penalties in trying to push all at once. Here is a link for your convenience:
forum.appian.com/.../Messaging_Best_Practices.html
Pay special attention to "passing data by reference" to the sub-process and ensuring the payload itself is small.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data