The article discusses how Dynamics 365 Business Central handles incoming web service calls. The author explains that Business Central has operational limits, including a per-user limit for OData service calls. These limits help improve concurrency and throughput. The author also discusses the handling of incoming web service calls by the NST (Navision Server Tier) and the potential issue of transaction consistency when spreading calls across different NSTs. To prevent this problem, Microsoft is introducing the concept of user sessions, where incoming requests are spread across different NSTs based on the user initiating the request. The author suggests using API batch calls and an intermediate layer for caching and queuing requests as solutions for handling large volumes of incoming web service requests.
Login now to access my digest by 365.Training