In this week's newsletter we will talk about running background tasks in ASP .NET Core. After reading this newsletter, you will be able to set up a background task and have it up and running within minutes. Background tasks are used to offload some work in your application to the background, outside of the normal application flow. A typical example can be asynchronously processing messages from a queue. I will show you how to create a simple background task that runs once and completes. And y...| www.milanjovanovic.tech
Iron Suite for .NET: the full office suite from Iron Software - PDF, OCR, Excel, Barcode, WebScraper | Get All 10 for the Price of 2.| ironsoftware.com
Read this case study to learn how Opyn Market used IronOCR to automate their invoice processing.| ironsoftware.com
Modular monoliths are becoming more popular in the software engineering community. The allure of Microservices is becoming less compelling. We also have seasoned veterans of our industry saying you should reconsider: > You shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile. — Martin Fowler Modular monoliths give you the logical architecture of Microservices without the operational complexity. You can safely determi...| www.milanjovanovic.tech
.NET • ASP.NET Core • Software Architecture| www.milanjovanovic.tech
What happens when a message is retried in an event-driven system? It happens more often than you think. The worst case scenario is that the message is processed twice, and the side effects can also be applied more than once. Do you want your bank account to be double charged? I'll assume the answer is no, of course. You can use the Idempotent Consumer pattern to solve this problem. In this week's issue I'll show you: - How the Idempotent Consumer pattern works - How to implement an Idempotent...| www.milanjovanovic.tech