Dynamics Business Central (NAV)
Experts:
Scalable Integration Architecture in Dynamics 365 Business Central
-
Scalable Integration Architecture in Dynamics 365 Business Central
How can you design a scalable and upgrade-safe integration architecture in Dynamics 365 Business Central for handling high-volume asynchronous transactions between multiple external systems (such as eCommerce, WMS, and CRM), while ensuring data consistency, minimizing API throttling, and maintaining extensibility through AL event subscribers and background sessions without modifying the base application?
Iām particularly interested in best practices around:
Queue-based processing
Retry/error handling mechanisms
Performance optimization for APIs
Event-driven extensibility in AL
Upgrade-safe customization strategies
-
1 Reply
-
Key thing: don’t let external systems hit BC directly. Use a queue as a buffer, external systems drop messages, and you process in batches every 5-10 minutes. Prevents throttling when dealing with high volume.
For retries, do exponential backoff (1s, 2s, 4s) and set Job Queue to retry 5-10 times. Log everything so you can debug.
BC throttles at 6,000 requests per user per 5 minutes, so batch your requests (20 items per batch), use filtering, and prefer REST over OData.
For integration logic, use AL event subscribersāpublish events, let extensions hook in. This way, you’re not modifying BC’s base code, so upgrades won’t break anything.
Basic flow: queue ā background job ā event subscribers ā other systems. No direct API calls, no throttling issues. The buffering is the real game-changer.
Log in to reply.
