In my last post about serverless architectures for decoupling integrations between Dynamics 365 Business Central and external applications, I’ve talked about the usage of queues and Azure Functions for exchanging messages between different cloud applications.
One of the quite common and simplest schema presented in the post was the following:
In this schema there’s a Timer Trigger…
Continue Reading demiliani’s Article on their blog
Timer Trigger Azure Functions: handling retry policies
In my last post about serverless architectures for decoupling integrations between Dynamics 365 Business Central and external applications, I’ve talked about the usage of queues and Azure Functions for exchanging messages between different cloud applications. One of the quite common and simplest schema presented in the post was the following: In this schema there’s a…
Blog Syndicated with demiliani’s Permission
More About This Author
Array
Dyn365BC2022.08.15Dynamics 365 Business Central: quick reminder for some upcoming changes
Dyn365BC2022.08.09Dynamics 365 Business Central: filtering telemetry signals with Azure Monitor Data Collection Rules
Dyn365BC2022.08.02Testing Azure Functions performances with Azure Load Testing
Dyn365BC2022.07.26Dynamics 365 Business Central: report extensions and global variables in preview mode
