If let's say we have this design:
More than one business event gets triggered (each for a certain action) from d365 -- then it goes to service bus or event grid etc.. - middle ware pickups the BE, calls a certain custom service based on the payload in order to get all details -- then send to the other system.
Now let's say that the number of calls to different custom services based on different BEs triggered can cause DOS attack to D365.
I think DOS attack happens when alot of calls to d365 happen at the same time.
And since alot of BEs and custom services are going to be used and we are expecting hundred thousands of calls to d365, then we want to change this solution.
My thinking is that to avoid DOS attack, maybe we need to change the integration to be outbound and return all details needed.
Something like recurring integration..but would be that really a good approach? I mean this would mean records to be created in the queue at night when not needed. Especially if data is needed real time so recurrence might be 1 min in this case. (I think accurate real time can't be done using outbound right?)
Any ideas?
Hi Deldyn,
There are various ways to create integrations. Without knowing details about the integration requirements and connectivity options from the other applications which should be connected, it is hard to say what would be the best approach. Using several different ways could also be considered.
The Dynamics 365 service is protected with throttling to avoid too many calls that can influence the performance for users working in the application. When you hit the throttling limits with your numbers, then indeed, you can check for other options. I always challenge the need for real time. Only consider that when there are valid requirements.
André Arnaud de Cal...
292,031
Super User 2025 Season 1
Martin Dráb
230,868
Most Valuable Professional
nmaenpaa
101,156