Microservices are easy—until they need to communicate reliably. Join Roland Guijt on Pluralsight to learn how to build resilient microservices with NServiceBus, covering messaging, workflows, and the patterns real distributed systems depend on.

"It would be foolish to try implementing a service discovery scheme on your own when good options already exist, unless service discovery is specifically your business domain." The 5th Fallacy: Topology doesn't change, on our blog:

See how you can send #NServiceBus messages from an #ASPNetCore #WebAPI application. #samplecode

Stop organizing code by layers nobody thinks about. Start organizing by features everyone understands. Vertical Slice Architecture helps you build simpler, more maintainable .NET apps. Read more about this architectural style, when to use it, pros and cons in this article

Get up to speed on running #NServiceBus in a #Docker container. Check out the details of Docker hosting here

A consolidated view of messages makes patterns and anomalies easier to spot. See how teams review system-wide message activity using the Particular Service Platform

Your company acquired a competitor that uses the *other* cloud vendor? No problem. You can integrate any system using the NServiceBus.Transport.Bridge

Have you used a message queue before? See how NServiceBus makes building these systems faster and easier

Watch @mauroservienti show how to design a UI that effectively combines data from multiple microservices into one display in this webinar recording: All our aggregates are wrong

When one microservice fails, does everything fail? It shouldn’t. The Bulkhead pattern isolates failures so one problem doesn’t sink your entire system. A great .NET resilience pattern worth understanding.

It's 2am and messages won't process. Where are you going to turn? Get 24x7 critical support (even for MassTransit/Rebus/Brighter systems) with 5-hour or even 1-hour response SLA from the experts at Particular Software for as little as $1000 per month.

When a workflow becomes complex, it is easy to lose track of how messages actually move through each step. The Particular Service Platform flow diagram brings that movement into focus.

Synchronous calls optimize for simplicity. Messaging optimizes for reality. If you're building distributed systems in .NET, understanding queues, topics, and async communication is essential.

Did you know you can use #NServiceBus to receive #RabbitMQ msgs from any platform? Get the sample code!

File > New > Distributed system

Which AWS technologies are right for your distributed system? Our architecture guidance has you covered.

Learn how to use NServiceBus saga timeouts to model the concept of time without the need for unreliable batch jobs

In this video, @indualagarsamy talks about the intersection of #DDD as a software discipline with #messaging as a technology counterpart

See how to blend #SignalR and #NServiceBus when dealing with occasionally connected, transient clients in this sample

A missing config value won't stop your .NET service from starting. It'll silently break at 2 AM in production. IValidateOptions<T> with ValidateOnStart() prevents this: your service won't start with bad config, and the validator has full DI access for cross property checks. By Bart Wullems.

Have you looked at C# 14's extension members yet? You can now define extension properties, extension operators, and static extensions. It's the biggest change to how you extend types since extension methods shipped in 2007. Post by Dirk Strauss.

Curious what ghost messages are? Find out with @SzymonPobiega this webinar

When a process crashes while holding a lock, what happens to the resource? Most teams don't find out until production teaches them. Chris Woodruff explores why indefinite locks are a liability in distributed systems and what to reach for instead.

Does your search need to understand meaning or just match exact text? That distinction is the core of what vector databases solve, and it's simpler than most explanations make it sound. Great walkthrough from @irina_scurtu.

Exceptions are a security boundary, not just a reliability concern. Your logs should have everything; your clients should have nothing they didn't need to know. Correlation IDs bridge the gap. Practical guide by Adrian Bailador.

In a theme park, you need to monitor how many people can ride a ride and which rides have the longest lines. Distributed software systems aren't much different! Maximizing fun (and profit) in your distributed systems, on our blog:

Most enterprise systems aren't algorithmically complex. They're workflow complex. Yet teams pour energy into implementation details instead of the much harder question: what exactly should we be building? @CodeOpinion explores why that matters.

Events as notifications vs. event sourcing vs. async messaging. Teams treat these as the same thing all the time, and that's where architectural mistakes start. Derek Comartin @codeopinion explores why these keep getting conflated.

Our step-by-step #NServiceBus tutorial teaches the basic concepts of async messaging as well as the NServiceBus API

“Although bandwidth keeps growing, the amount of data and our need for it grows faster. We'll never be satisfied.” The 3rd Fallacy of Distributed Computing: Bandwidth is infinite

Your messaging workflow shouldn’t be a mystery. A visual timeline of message flow makes it easier to see what happened and diagnose issues. Take a look at the Particular Service Platform.

If you’re using async/await to solve distributed system problems, you might be using the wrong tool. Async/await removes waiting. Messaging removes coupling. Async helps your threads scale. Messaging helps your system scale. Irina discusses this in her latest blog post

Have you heard of the fallacies of distributed computing? In the currently free Distributed Systems Design Fundamentals course, @udidahan walks you through all of them, even the ones you didn’t know existed. #DSDF https://go.particular.net/l/27442/2026-03-12/8z7grc

Application performance always matters. Sometimes critically, sometimes subtly, but it’s never irrelevant. While many developers rightly caution that “premature optimisation is the root of all evil,” the opposite…

In a theme park, you need to monitor how many people can ride a ride and which rides have the longest lines. Distributed software systems aren't much different! Maximizing fun (and profit) in your distributed systems, on our blog:

Learn how to use NServiceBus saga timeouts to model the concept of time without the need for unreliable batch jobs

Seeing all message activity in one place changes how you debug. The All Messages view in the Particular Service Platform makes that possible

See how to blend #SignalR and #NServiceBus when dealing with occasionally connected, transient clients in this sample

“Although bandwidth keeps growing, the amount of data and our need for it grows faster. We'll never be satisfied.” The 3rd Fallacy of Distributed Computing: Bandwidth is infinite

Race conditions aren't bugs. They're what happens when reality hits your architecture -Requests arrive together, Messages retry, Users double-click, Networks delay things.…

Stop Losing Messages: How the Outbox Pattern Solves the ‘Dual Write’ Problem in .NET. The Outbox Pattern turns a brittle “dual write” problem into a reliable, asynchronous workflow

Our step-by-step #NServiceBus tutorial teaches the basic concepts of async messaging as well as the NServiceBus API

Distributed systems patterns aren't about complexity. They're about damage control. Every pattern exists because something failed in production somewhere. Read about 8 such patterns in this article

You know what they say about making assumptions. Sequence diagrams in the Particular Service Platform help create a visual timeline for messaging workflows, validating what you think is happening, and identifying what actually is

Implementing Redis caching is an effective way to improve performance in high-traffic applications. By storing frequently accessed data in memory, Redis allows applications…

Curious what ghost messages are? Find out with @SzymonPobiega this webinar

Zero Trust in the cloud is like “no VIP wristbands” for your apps — every user, device, and request gets checked, every time. Strong identity, least-privilege access, and continuous verification keep things friendly but safe

Event-driven architecture is a powerful design pattern used in modern distributed systems to build scalable and responsive applications. By using event producers, consumers, and message…

Optimizing Bulk Database Updates in .NET: From Naive to Lightning-Fast. This article by Milan Jovanović discusses 7 different approaches and their performance while optimizing for bulk updates in PostgreSQL

Existing systems built with MassTransit can be integrated with new NServiceBus systems using a message pipeline behavior in the NServiceBus endpoints to translate incoming MassTransit messages into a shape that can be successfully processed. #samplecode