Looking for a safer way to correct message data when something goes wrong? The Particular Service Platform provides a structured approach to editing messages without failure

In a hospital ER, birthdate is nullable because patients sometimes arrive unconscious. In a pharmacy, birthdate is a rule that controls what patients get access to which drugs. How do we integrate these two systems?

AI agents will need to train on their conversations with users in order to continue to learn. However, doing so without explicit data indicating whether or not a given response solved a given problem will make it very difficult to determine which responses to weight higher than others.

JetBrains Developer Advocate Rachel Appel describes deceptive UI practices. She cautions developers and marketers to avoid these practices, which often lead to a loss of trust and other long-term problems. She informs users what to watch out for, and how to remain vigilant.

Reactive resilience strategies are essential tools for building reliable distributed systems. Each strategy addresses different failure scenarios: * Retry handles transient failures

Indefinite locks belong to a world where processes never crash and networks never split. That world does not exist. In a distributed system, “I hold the lock” can mean…

AI generated code ships 55% faster but shows 41% higher churn. When you're adding features at twice the speed, architectural mistakes compound at twice the rate too. That's the velocity paradox this article explores. by Dariusz Gafka

New blog series translating Unmesh Joshi's Patterns of Distributed Systems catalog into #CSharp and #dotnet. Covers 30+ patterns: leader election, write ahead…

Containerizing a #dotnet service and calling it "cloud native" is easy. Making it survive restarts, scale correctly, and deploy without dropping requests is where most teams struggle. This guide covers the operational gap. by Sudhir Mangla

The Particular Service Platform provides early signals to help your team respond before things escalate. See how health checks help your team stay proactive in the face of event failure

How quickly can your system identify what patient data was accessed, by whom, and when? HIPAA's Breach Notification Rule gives you 60 days. If your logging can't answer that, it's an architecture problem, not a tooling one. via Sudhir Mangla

Ever scaled a service from one instance to two and had scheduled jobs suddenly fire twice? That's accidental multi leader behavior, and it's more common than you'd think. Good walkthrough on implementing lease based election in C#. via Chris Woodruff

Sometimes the best takeaway from a source generator review is that the underlying API is already well designed. If the manual code is simple and performant, maybe a generator isn't needed. Good analysis from @andrewlocknet on #dotnet metrics

#dotnet has had built in metrics APIs since .NET 6, but many teams still aren't using them for custom application or business metrics. This post by @andrewlocknet covers what's available and how to get started with System.Diagnostics.Metrics

A lease is a lock with a deadline. The hard rule: if you can't renew, you stop acting like the owner. This walkthrough covers atomic acquire, atomic renew with Lua, token checked release, and a leader election loop using Redis and .NET. By Chris Woodruff

Ever added a unique constraint for idempotency and still ended up with duplicate side effects? Derek Comartin walks through why inbox tables don't protect external calls and five strategies to design for "effectively once" instead of "exactly once."

Sometimes message data is just wrong. So how do you fix it without causing more damage? See how controlled editing works on the Particular Service Platform

Production systems will fail. When they do, your recovery depends on how well you can see what went wrong and why. This intro to OpenTelemetry covers why observability matters and what it takes to get started with the emerging standard. via @nimblepros

Don't connect a WPF app to #NServiceBus, forward those events to #SignalR instead. See how!

Check out our sample on hosting #NServiceBus endpoints in #Docker Linux containers

Learn how to build an NServiceBus saga to model a situation where you call one shipping provider, and set a timeout so that if it doesn't respond within your SLA, you can ship via a backup shipping provider instead

"Tired of dealing with duplicate messages or outbox patterns in your .NET apps? ✅ Use PostgreSQL for messaging AND persistence ✅ Handle everything in a single atomic transaction

Use #NServiceBus (even) in legacy systems using SQL Server. See how to get started with this sample

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

In event-driven systems, large events are a design smell…keep them as small as possible. Services should really only share IDs and maybe a timestamp to indicate when the information was effective. Putting your events on a diet, on our blog:

When a 3rd party dependency goes down, #NServiceBus's monitoring solution can let you know

Clear insight into failed messages can make recovery work far less stressful. Retry failed messages with confidence using the Particular Service Platform

Logging isn't about logging more — it's about logging what you actually need to diagnose a failure at 3AM. Log smarter and with intent. Read about some of the common anti-patterns in logging and their practical solutions in this blog

"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?

In this video, @DavidBoike describes what it's like to work here at Particular Software, the fully-distributed software company with no office and no managers

In event-driven systems, large events are a design smell…keep them as small as possible. Services should really only share IDs and maybe a timestamp to indicate when the information was effective. Putting your events on a diet, on our blog:

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