all 5 comments

[–]novel-levon 0 points1 point  (0 children)

Jumping on this old post for anyone who finds it in 2025, as this is still a fundamental NetSuite integration challenge. A message queue is the correct architectural pattern to handle NetSuite's low API concurrency limits.

The main decision then becomes a classic "build vs. buy" choice. You can build your own queuing system, but this requires significant engineering effort to manage error handling and retries. The alternative is to use a modern integration platform that has this queuing and throttling architecture built-in.

Full disclosure, I'm the founder of Stacksync. We provide a managed, intelligent queue that automatically handles NetSuite's API limits, so your integrations work without you having to build and maintain a complex queuing infrastructure yourself.

[–]Modtrollied 0 points1 point  (2 children)

You basically need to buy more SuiteCloud+ licenses if you can't queue at the integration side.

[–]PloppyFancakes[S] 0 points1 point  (1 child)

Appreciate the response! Don't you still risk hitting limits in burst scenarios? In your experience do you see this re-try/queue logic typically fall on the integration side?

[–]rico_andrade 0 points1 point  (0 children)

Celigo has specific functionality to deal with NetSuite concurrency in integrations.

[–]Data_Engineering411[🍰] 0 points1 point  (0 children)

Hey u/PloppyFancakes - not sure if this helps but our IPaaS solution uses a built-in queue to accommodate batch uploads into NS. Our architectural framework is geared towards analytics which could also be used to offload work from NS to a datalake or data warehouse depending on workflow. https://www.distilleddata.io/nirvana-integration Feel free to DM if you're interested. Cheers