Sumit S Shevade

Azure Infrastructure for Asynchronous Processing This article's main focus is on the infrastructure provided by Microsoft Azure for seamless processing. Article on  Asynchronous Processing  can be found here  ☺️ Microsoft Azure provides us various things for application to work in bits and pieces. It helps in managing long-running processes; Azure provides: Azure Service Bus (Messaging) Topic Queue Storage Queue (Storage) WebJobs Function Apps Service Fabric We'll also try to touch on Microservices. There is one confusing part we need to understand is Queue ... As it is in the Azure Service Bus as well as in the Storage. Azure Service Bus has Topics and Queues. Storage has Table, Blob, File Storage and Queues. The major difference between storage queues and service bus queues is well documented here . In this architecture as well we need an end-point to which consumers will hit and a message will go to a queue, which will be consumed by...

Asynchronous Processing C# Programming context To understand what is Asynchronous Processing, the prerequisite is to understand what is Synchronous Processing. Basically, there are two main things involved in this: Client Server Client:  Sends the request to a server and keeps waiting until it receives the response. During the process, it keeps loading and needs a constant connection to the server. Server:  It processes the request received by the client and sends the response. If the process is long-running, sometimes the server goes out of memory or shows timeout error. Due to this, it is not suitable or recommended for long-running operations. There are multiple problems with this approach... Let's discuss a few of them: Bad user experience The server needs to be very powerful as it may need to work on concurrent requests Server consumes a lot of resources To overcome this problem, Microsoft .NET Framework 4.0 introduces a new Task Parallel...