https://thedotnetblog.com/tags/reliability/Articles, tutorials and insights from the .NET community.Hugoen@thedotnetblog (The .NET Blog)@thedotnetblogMon, 04 May 2026 00:00:00 +0000https://thedotnetblog.com/news/emiliano-montesdeoca/azure-service-bus-per-message-settlement/Mon, 04 May 2026 00:00:00 +0000Emiliano Montesdeocahttps://thedotnetblog.com/news/emiliano-montesdeoca/azure-service-bus-per-message-settlement/Why all-or-nothing batch handling hurts reliability, and how per-message settlement improves Service Bus workflows for .NET.<p><a href="https://devblogs.microsoft.com/azure-sdk/per-message-settlement-azure-service-bus/">Fixing All-or-Nothing Batch Processing in Azure Service Bus</a> is worth a close look if you are building or operating .NET systems at scale.</p> <p>From my perspective, the important part is not the headline feature but how quickly a team can convert it into a safer, repeatable engineering workflow.</p> <h2 id="why-it-matters-for-net-teams">Why it matters for .NET teams</h2> <p>Most teams are balancing delivery speed, platform consistency, and governance. This update is useful because it gives you a more concrete path to improve one of those constraints without rewriting everything.</p> <h2 id="practical-next-steps">Practical next steps</h2> <ol> <li>Validate the feature in a small .NET pilot with production-like data.</li> <li>Add clear rollback and observability checkpoints before broader rollout.</li> <li>Capture the implementation pattern in your internal templates so other teams can reuse it.</li> </ol> <h2 id="source">Source</h2> <ul> <li>Original article: <a href="https://devblogs.microsoft.com/azure-sdk/per-message-settlement-azure-service-bus/">https://devblogs.microsoft.com/azure-sdk/per-message-settlement-azure-service-bus/</a></li> </ul>