Overusing async, unmanaged resources, and DateTime pitfalls are still common in C#. Read about some of the common mistakes in C# that can cost you and ways to steer clear of them in this C# Corner article

Understanding how a saga behaves across its full lifecycle can be tricky. But it doesn’t have to be! With the Particular Service Platform, you’ll see a visual timeline…

Allow your endpoints to talk to each other, even if they use different transports. NServiceBus.Transport.Bridge is now available

Watch this video for a deep dive into Async in .NET with @danielmarbach. Even if you think you know async inside and out…you probably don't

Ensure reliable message processing with NServiceBus’s PostgreSQL transport. Choose the transaction mode that fits your needs and keep your data safe.

Just because your handler is idempotent doesn’t mean side effects (like charging a card) are. Concurrency + external APIs can still bite you. Read the latest article by @codeopinion that discusses this problem and some solutions

We have a NuGet package called ParticularTemplates which includes templates you can use with dotnet new, including this template for creating an NServiceBus #Docker container host

If you've ever wondered why you shouldn't just use RabbitMQ directly, this interview with Udi Dahan can be quite revealing

You can't future-proof software architecture — the future just breaks assumptions. What you can do is control where change ripples through your system. Read more in this blog by @codeopinion

Kafka, RabbitMQ & SQS all move messages — but cost, scaling behavior & real production surprises matter more than on-paper benchmarks. Lessons learnt the hard way discussed here..

Your system doesn't have to be 100% #serverless. Check out an example of how @AzureFunctions can be used to perform a cleanup activity on an NServiceBus system using Azure Blob Storage to store blobs with the Claim Check pattern

"Distributed systems do not fail because you missed a feature. They fail because responsibility is unclear. Two nodes act, both think they are right, and your data becomes a debate.…

Watch this video for a deep dive into Async in .NET with @danielmarbach. Even if you think you know async inside and out…you probably don't

"What is missing from this process is an understanding of why tests work in the first place. Tests work best when you have seen them fail."

If you're updating to .NET 10 and using Azure Storage Queues, you'll need this patch to deal with a build error due to a breaking change Microsoft introduced around the AsyncEnumerable…

Does debugging failed messages feel like guesswork? A focused retry workflow makes context clear and recovery safer. See how to handle failed messages in the Particular Service Platform

Did you know you can completely replace Windows File Explorer?

We have a NuGet package called ParticularTemplates which includes templates you can use with dotnet new, including this template for creating an NServiceBus #Docker container host

#RabbitMQ has clients for just about any language, and #NServiceBus can process messages from all of them

If you've ever wondered why you shouldn't just use RabbitMQ directly, this interview with Udi Dahan can be quite revealing

When a workflow spans many messages, it becomes impossible to see what happened first, which state changed, and why a timeout fired. But with the Particular Service Platform, the impossible becomes possible. Take a look to see it in action.

"2413 exceptions last night." … "Only? Did one of the batches crash?" If this sounds like a conversation you've had recently, find out a better way to deal with exceptions. I caught an exception. Now what?

"Today, we have DSL and cable modems; tomorrow, fiber may be widespread. But although bandwidth keeps growing, the amount of data and our need for it grows faster. We'll never be satisfied." The 3rd Fallacy: Bandwidth is infinite

Great news, NServiceBus version 10 has been released! Check out the announcement for details and a link to the upgrade guide.

Don't miss our live webinar in less than 48 hours! Even if you can’t make it live, register, and we’ll send you the recording when it’s available. Effortless Distributed Systems with Aspire, with @jasontaylordev

Many systems become harder to evolve because early decisions were made to support imagined scenarios. @CodeOpinion shows how clear boundaries, simple models, and decisions grounded in present requirements avoid the speculative features that make architecture brittle over time.

We had so much fun playing ACKS and Exceptions with attendees at #NDCLondon that we thought it would be a shame to not share it with everyone.

Most developers know how to build services, but what about wiring them together reliably, debugging failures, and deploying without breaking everything? Find out in our live webinar with @jasontaylordev on February 4.

Switching between tools adds friction when diagnosing issues; the All Messages view in the Particular Service Platform keeps message review and filtering in one place

Join William Brander today at #NDCLondon at 13:40 in Room 3 for Indiana Jones and the Temple of Legacy Code, a dive into the unexplored mysteries of lagacy code systems. 🤠🛕🐍

Curious how to remove friction from architecture, orchestration, messaging, observability, and deployment? Find out with @jasontaylordev in our live webinar on February 4.

Join @jasontaylordev for a live webinar: Effortless Distributed Systems with Aspire, February 4 at 01:00 UTC. Learn how Aspire orchestrates services with reliability & observability, NServiceBus improves resilience, and Azure Developer CLI streamlines dev→cloud.

Zero downtime sounds simple until a schema change breaks older code paths that are still in flight. In this post, Milan Jovanovic uses a password hashing upgrade to show how phased transitions keep systems stable during live migrations.

Failed messages are like Thanos: Inevitable. What matters is being able to see why they failed and retry them safely once the issue is fixed. Seems practical, right? See how teams handle retries without making things worse

When building a UI, if one microservice has to ask for data from another microservice, then those services aren't truly autonomous. Learn how to build a composite UI the right way from @mauroservienti in this video

How do you keep your Minimal API from leaking database structure into client code and JSON? Chris Woodruff explores why clear data boundaries matter and why stable contracts help protect clients as systems evolve.

Async code looks simple until a small blocking call creates a deadlock that only appears under load. This talk shows how context capture, sync boundaries, and thread starvation create surprising bottlenecks across services.

Ready to get the most out of your messaging platform? Join Poornima today at #NDCLondon at 10:20 in Room 1 for Beyond Pub/Sub - Advanced Messaging Patterns where she will dive into patterns that address the toughest challenges in distributed systems.

Systems that process frequent updates or partial state changes often struggle to stay responsive and hit limits. This post explains why those patterns put pressure on storage…

Distributed systems often hide race conditions that only show up under load. In this post, Oskar Dudycz explains how a read model rebuild can miss events even when the design looks correct on paper, and why making that blind spot observable leads to safer systems.

"If we…received an HTTP timeout, we would have no way of knowing if the server received the data and was simply unable to respond or if, rather, the data never arrived at all." The 1st Fallacy of Distributed Computing: The network is reliable

The saga diagram gives teams a way to inspect the full lifecycle of a saga instance, from incoming messages to outgoing actions, all in one place. See what that looks like in the Particular Service Platform.

Migrating from on-prem to the cloud? Don't forget your bridge

What happens when an architect approaches a system with both a wide lens and a simplicity-first mindset? In this article, Chris Woodruff shows how that combination supports clearer decisions and more predictable outcomes.

Have you ever wondered why retries and idempotent APIs still fail to prevent lost events inside a service? This article breaks down how the Outbox pattern closes that gap and why it pairs naturally with idempotent consumers.

Learn how to build something like Gmail's Undo Send, where there's a "Buyer's Remorse" period before an action is made permanent, using NServiceBus saga timeouts

Static analysis, technical debt as “interest”, and CQLinq-powered queries for large .NET codebases all come together in this new Modern .NET Show episode on NDepend with Patrick Smacchia. Listen here:

Check out how to easily create an NServiceBus #Docker container by using dotnet new and our templates package

Are you going to #NDCLondon? There is an amazing agenda, and we're proud to have some of our speakers there. Check out the schedule to see what talks Poornima Nayar and William Brander have in store for you! @NDC_Conferences

Do you feel the weight of complexity dragging down your system? You're not alone. Watch this webinar recording for strategies that might help. Finding your service boundaries: a practical guide with @adamralph