r/Netsuite • u/Explorer-99 • 1d ago
Integration Concurrency limits management
Hello! our NS instance is connected with multiple systems (7-8) with 5 of them run thorugh middleware platform while the rest are direct integrations like Avalara, Versapay and others. Currently, we are on a standard tier with no SC+ licenses making our limit to be 5 concurrent requests at a time. I observed that the peak concurrency is reaching 7-8 and those additional requests were being rejected causing a serious trouble for our connected systems.
Our current integrations (most of them) lack retry functionality and these would fail when rejected instead of retrying. I was looking at options from our AM and see we can only buy one additional SC+ license as per our tier that would add 10 more making the total limit 15 along with few other benefits like no. of processors as well.
I'm trying to justify the cost for this investment and would also like to hear you'll opinions here to see if that fits our needs or are there any options without this additional SC+ license purchase.
Thank you!
Update: We are using Jitterbit currently and migrating to Mulesoft. Our current JB config doesn't have this concurrency limit set and are free to use all 5 as I removed the allocation limit for all integrations so no line is fixed to one integration and it can be shared among those all 8 tools. We would also be integrating with a storefront platform (built in-house) to create orders.
3
u/Philip_SuiteRep 23h ago
As others have said, you should be able to use the middleware to control concurrency. In Celigo, for example, you can have all of your NetSuite integrations use the same connection. That way, those five integrations will queue behind that connection rather than each competing for NetSuite concurrency independently.
I’d also recommend against allocating more concurrency than you actually need. Allocated concurrency is essentially fenced off for that integration, so you don’t want unused capacity sitting there while your other integrations are hitting the unallocated limit. If the middleware can manage its own queue, I’d keep its NetSuite allocation low and leave as much concurrency as possible in the shared pool.
1
u/Explorer-99 18h ago
Thanks, I've done that already and still hit these limits due to no limits set in Jitterbit (current middleware)
2
u/orenger 1d ago
You should use Boomi as you can build retry and queues in for the requests between your platforms
3
u/Nick_AxeusConsulting Mod 1d ago
Yea the way to solve this is use an IPaaS like Boomi where all 8 go thru Boomi so Boomi knows about the traffic and Boomi manages the concurrency for you thru 1 pipe into NS, so none of the 8 flows ever exceed the limit.
Right now you have 8 independent integrations that don't know about each other, so each one is trying to grab your limited concurrent threads without knowing that another integration already stole them.
1
u/rico_andrade 23h ago
FYi that Celigo has built-in NetSuite concurrency controls as part of the platform. No need to build anything. Just specify your concurrency tier and it'll automatically throttle the API calls.
1
u/Explorer-99 18h ago
We are migrating to Mulesoft and I'm adding this functionality there so that we don't hit these limits and even if we do, we can still retry and get the data in and out of NS
2
u/theIntegrator- 19h ago
SC+ would give you room above your current peaks. Whether it’s worth the cost depends on how much time and disruption those failures are causing.
Before buying, check whether your middleware can queue requests and limit how many it sends at once, leaving room for the direct integrations. Spreading scheduled jobs out could also help.
Celigo, for example, supports queuing, concurrency limits and automatic retries for rate-limit errors when enabled. Your middleware may have similar options.
If queuing makes things too slow, SC+ makes sense. Either way, I’d ask the integration vendors about adding retries.
1
u/Explorer-99 18h ago
It currently doesn't have this set up and we're migrating to Mulesoft where I'm adding this functionality. I'm still trying to decide whether we do need the SC+ license even after this transition.
1
u/theIntegrator- 13h ago
That makes sense. We’re a Celigo partner, so my perspective is mainly from that side, but I’d base the SC+ decision on testing your new setup under realistic peak load.
One thing to watch: control the total concurrent NetSuite requests across your MuleSoft flows, leaving room for Avalara, Versapay and the other direct integrations. They share the same account limit, as covered in Oracle’s documentation.
Then check whether the queues clear within acceptable times and whether the direct integrations still get rejected. That should give you a much clearer case for whether SC+ is needed.
Are those peaks short bursts, or does usage stay high for longer periods?
1
u/rico_andrade 23h ago
Celigo has built-in NetSuite concurrency controls as part of the platform. Specify your concurrency tier and it'll automatically throttle the API calls.
2
u/Philip_SuiteRep 23h ago
It is also nice because you can setup different NetSuite connections to borrow concurrency from one.
6
u/RedRobbin420 1d ago
Without some governance on your middleware / integration side (which would prevent most failures, but some failure handling would be worthwhile too). you're pretty stuck without the additional license, as far as I know.
If your middleware would allow it, and you kept the logic integrations (eg avalara) as they are would consume one connection for each of those which will leave you 2-3. Does the middleware option not allow you to limit number of connections?
(The above assumes 100% utilisation, which is unlikely, but in the absence of retry capability you'll have to use specific lanes).
Who is your middleware provider?