Post

A client once told me about a .NET Worker Service that had worked without trouble for months. It read messages from a queue, applied business logic, and updated a database. The code did what it was supposed to do, so nobody had much reason to question it. devandreacarratta.it/en/technical...

devandreacarratta.it.NET Worker Service: the code was right, the place was wrongA .NET Worker Service stopped processing for 60 hours. My own batch jobs faced a similar problem. Here is why correct code still needs the right infrastructure.

0 reposts0 likes

There was one detail we had overlooked: the service ran on a personal computer. When that computer was switched off on an ordinary Friday, message processing stopped with it. By Monday, around 60 hours of work had accumulated. The code hadn’t failed; its hosting environment had.