Thanks battk. We are using TBA, and this is for a...
# suitetalkapij
Jesse Davis
06/06/2019, 6:56 PMThanks battk. We are using TBA, and this is for a .NET webapi project. Before we rolled-our-own queuing mechanism, I noticed there are some some psuedo-active nuget packages and thought there might possibly be some third-party drop-in solutions for managing the requests?
d
David Durst
06/07/2019, 6:34 AM@Jesse Davis I am not a .NET programmer so I can't speak directly to the objects you should be using to accomplish this... however... since they are kind of standard KIT for all languages I will you have something like them.
David Durst
06/07/2019, 6:35 AMWe use SOAP API but all of our requests are update multiple request because updating a single record at a time when doing bulk processing is just a horrible waste of transport layer time
David Durst
06/07/2019, 6:36 AMWe build out a queue of jobs and we optimize the size of those jobs (Size measured in records) based upon testing... currently we have found that most of the time 20-30 records at a time is a sweet spot... but please do your own testing
David Durst
06/07/2019, 6:36 AMOnce that Queue is setup we spin up N threads (N correlating to the concurrent paths you have available in your NS implementation.
David Durst
06/07/2019, 6:37 AMEach thread has a loop and consumes a single job per iteration.
David Durst
06/07/2019, 6:37 AMIf you want to get more stream functionality like you can have produce and consumer threads also.